feat(kubernetes-agent): add optional hostNetwork for NFS server pod#508
Open
manishprivet wants to merge 2 commits intoOctopusDeploy:mainfrom
Open
feat(kubernetes-agent): add optional hostNetwork for NFS server pod#508manishprivet wants to merge 2 commits intoOctopusDeploy:mainfrom
manishprivet wants to merge 2 commits intoOctopusDeploy:mainfrom
Conversation
Add persistence.nfs.hostNetwork option to allow the NFS server pod to use the host network. This is useful in environments with network policies that block traffic from the NFS CSI driver to the NFS server pod. When the NFS CSI driver (which runs with hostNetwork: true) attempts to mount the NFS volume, the traffic appears to come from the node IP rather than a pod. Network policies using namespaceSelector cannot match this traffic, causing mount failures with 'time out' or 'Name or service not known' errors. Setting hostNetwork: true on the NFS server pod allows it to bypass network policy enforcement, enabling successful NFS mounts in restricted environments.
|
|
|
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
2 participants
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.
Summary
Add
persistence.nfs.hostNetworkoption to allow the NFS server pod to use the host network.Problem
When network policies are applied to a namespace, the NFS CSI driver cannot mount the NFS volume because:
hostNetwork: true, so traffic appears to come from node IPsnamespaceSelectorcannot match traffic from node IPsSolution
Add an optional
hostNetworksetting for the NFS server pod. When enabled:hostNetwork: truednsPolicy: ClusterFirstWithHostNetto ensure cluster DNS still worksUsage
Changes
charts/kubernetes-agent/templates/nfs-statefulset.yaml: Add conditional hostNetwork and dnsPolicycharts/kubernetes-agent/values.yaml: Addpersistence.nfs.hostNetworkoption (default: false)