Add ability to configure dnsPolicy
#59
Open
Conversation
This file contains 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
|
Hi! Thanks for the contribution. Just bump the version of the chart and we can merge. A patch version bump should be fine for this change. |
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.
According to Kubernetes' documentation the
dnsPolicyshould be set toClusterFirstWithHostNetwhenhostNetwork: trueis set. This PR adds the option to configurednsPolicyfor bothnodeandcontrollerparts of the Helm chart.This solves an issue I was facing where a host was resolved by the controller (and so the NFS mount was configured) but was not resolved when the volume was mounted.
This is what
csi-driver-nfsdoes: https://github.com/kubernetes-csi/csi-driver-nfs/blob/096163569b792c4eb38fcf652e8ef2c3a8a5060b/charts/v4.9.0/csi-driver-nfs/values.yaml#L102