-
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
fix envvars in args #4037
fix envvars in args #4037
Conversation
ci check this |
/assign @woopstar |
@LuckySB Do you have a fix for the other roles also? I haven't searched for the root cause elsewhere, but this PR looks like it's only applicable to windows nodes. We should be able to set hostnameOverride in the config used by kubeadm if that's not working properly yet. |
/assign @chadswen |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: LuckySB If they are not already assigned, you can assign the PR to them by writing 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 |
The win_nodes role adds restrictions to the daemonset kube_proxy, so that it runs only on linux-based nodes. I also want to note that in version 1.13.0, this patch is no longer necessary to apply. |
@LuckySB just hit this when deployed v1.13.2 with Kubespray (from master branch).
@chadswen I'm a bit confused here as well, but this patch seems to be applied on linux nodes as well 🤷♂️ not sure why it's called |
@LuckySB with this PR, I get the following result after deployment:
This is better, but there's still duplicate entries. |
3542728
to
b61777a
Compare
Thank you very much. |
You're welcome @LuckySB I was also thinking that considering that this patch is only needed for k8s version < 1.13.0, it may be easier to just apply a conditional on the whole task block, here: kubespray/roles/win_nodes/kubernetes_patch/tasks/main.yml Lines 34 to 35 in 0888f65
by adding:
and remove the search conditional entirely. |
Of course you are right. from version 1.13 this patch will not be needed But if you add this condition and remove the condition with the search, then on the version less than 1.13 every time you start the kubespray, the line '--hostname-override' will be added |
Ok, I see your point.
Thanks @LuckySB
…On Sat., Jan. 26, 2019, 12:47 Sergey ***@***.*** wrote:
I was also thinking that considering that this patch is only needed for
k8s version < 1.13.0, it may be easier to just apply a conditional on the
whole task block, here:
kubespray/roles/win_nodes/kubernetes_patch/tasks/main.yml
<https://github.com/kubernetes-sigs/kubespray/blob/0888f65b24ec58bd84c5d6d5dd7d25aed0a7229e/roles/win_nodes/kubernetes_patch/tasks/main.yml#L34-L35>
Lines 34 to 35 in 0888f65
<http:///kubernetes-sigs/kubespray/commit/0888f65b24ec58bd84c5d6d5dd7d25aed0a7229e>
when:
- not kube_proxy_remove
by adding:
- kube_version is version('v1.13.0', '<')
and remove the search conditional entirely.
Of course you are right. from version 1.13 this patch will not be needed
But if you add this condition and remove the condition with the search,
then on the version less than 1.13 every time you start the kubespray, the
line '--hostname-override' will be added
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4037 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXJk7Or5w1-0V2phO79hhzHXmyR4Xhh_ks5vHJTAgaJpZM4Z855E>
.
|
Hey @chadswen! following our slack chat about this, do you think we can get this merged? |
fix env vars substitution error in hostnameOverride-patch.json
https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#use-environment-variables-to-define-arguments
I also want to note that in version 1.13.0, this patch is no longer necessary to apply.
https://github.com/kubernetes/kubernetes/pull/71283/files
#4036