Removing hostNetwork: true setting from CSI controller and node pods #71
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 this PR does / why we need it:
This PR is removing
hostNetwork : true
setting from CSI controller and node DaemonSet pods.With this change we are also setting
dnsPolicy: "Default"
for pod spec which allows pod to inherits the name resolution configuration from the node that the pods run on. Without this, when vCenter Host is specified by FQDN, pod cannot establish connection to vCenter, and results into this error -err: Post https://sc2-rdops-vm09-dhcp-60-181.eng.vmware.com:443/sdk: dial tcp: i/o timeout
This change is required to fix concern mentioned at #68 (comment)
With this change, we will be able to merge liveness probe change made in this PR - #68
We have verified liveness probe works fine on both node DeamonSet pod and controller pod when both pods are deployed on the same node.
Which issue this PR fixes
fixes #70
Special notes for your reviewer:
With the image built from this change, @RaunakShah has also verified
csinodes
is correctly populatingNode ID:
with actual node names and volume is successfully getting attached to the node.Release note: