fix: set ClusterFirstWithHostNet as default dnsPolicy #604
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?
/kind bug
What this PR does / why we need it:
fix: set ClusterFirstWithHostNet as default dnsPolicy
This PR also fixed a bug that controller should also set
hostNetwork: true
which requires in smb driver connection.https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-s-dns-policy
"ClusterFirstWithHostNet": For Pods running with hostNetwork, you should explicitly set its DNS policy to "ClusterFirstWithHostNet". Otherwise, Pods running with hostNetwork and "ClusterFirst" will fallback to the behavior of the "Default" policy.
Note: This is not supported on Windows. See below for details
Which issue(s) this PR fixes:
Fixes #600
Requirements:
Special notes for your reviewer:
cc @davidandreoletti
Release note: