Add ability to specify dnsPolicy in sidecar injector helm chart #7407
+5
−0
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.
Description
When enabling hostNetwork: true in the sidecar injector chart to resolve networking issues associated with using CNI on EKS, which results in the Kubernetes Control Plane being unable to access the sidecar injector webhook, it is often also necessary to set the pod's dnsPolicy to 'ClusterFirstWithHostNet' to prevent DNS issues.
The sidecar injector Helm Chart currently offers no ability to specify the dnsPolicy and hence it always reverts to the cluster default.
This straightforward PR adds the option to provide this value to the sidecar injector chart. If no value is explicitly specified, it continues using the cluster default per the existing behavior.
Issue reference
#4270
Checklist