Repository navigation
fix(helm): use cluster DNS for the node agent - #21
Merged
Merged
Conversation
Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Set dnsPolicy: ClusterFirstWithHostNet on the Snapshot agent DaemonSet.
The agent uses host networking. Without this policy, it falls back to the node’s DNS configuration, which may not resolve Kubernetes Service names. On a Liqo provider, this prevents the agent from reaching the consumer metadata API through curie-api.dynamo.svc.cluster.local, blocking checkpoint capture.
Which issue(s) this PR fixes:
Fixes #
How was this tested?
Special notes for your reviewer:
Covers both ordinary and remote metadata configurations. Host networking remains enabled.
The corrected chart has not yet been deployed for live capture/restore verification.
Does this PR introduce an API change?
NONE
Additional documentation, e.g. enhancement proposals, usage docs:
docs/operations/security.md documents cluster DNS for the host-networked agent.
Checklist