-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
hostnameOverride on a per-node basis in kube-proxy configuration with kubeadm #3708
hostnameOverride on a per-node basis in kube-proxy configuration with kubeadm #3708
Conversation
ci check this |
@mirwan Thanks! This bug has existed for a long time. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: riverzhang 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 |
977f41b
to
b380350
Compare
@riverzhang a lgtm as well please? |
/lgtm |
@@ -180,7 +180,6 @@ conntrack: | |||
tcpEstablishedTimeout: 24h0m0s | |||
enableProfiling: false | |||
healthzBindAddress: 0.0.0.0:10256 | |||
hostnameOverride: {{ inventory_hostname }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you remove this, then it wont be set unless you have win nodes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@woopstar Actually I was a bit astonished by the path of the role but couldn't see any restriction so I guess it will be set when kubeadm is enabled.
Supersedes PR #3612 (by addressing the issue described here https://kubernetes.io/docs/setup/independent/troubleshooting-kubeadm/#services-with-externaltrafficpolicy-local-are-not-reachable) and thus fixes #3610.