Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing hostNetwork: true setting from CSI controller and node pods #71

Merged
merged 1 commit into from
Oct 2, 2019
Merged

Removing hostNetwork: true setting from CSI controller and node pods #71

merged 1 commit into from
Oct 2, 2019

Conversation

divyenpatel
Copy link
Member

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 populating Node ID: with actual node names and volume is successfully getting attached to the node.

Release note:

Removing hostNetwork setting from CSI controller and node pods

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 1, 2019
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Oct 1, 2019
@dvonthenen
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 2, 2019
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: divyenpatel, dvonthenen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 2, 2019
@k8s-ci-robot k8s-ci-robot merged commit e886fb3 into kubernetes-sigs:master Oct 2, 2019
gnufied pushed a commit to gnufied/vsphere-csi-driver that referenced this pull request May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CSI Controller (ss) and CSI Node (ds) can't run on the same node
3 participants