-
Notifications
You must be signed in to change notification settings - Fork 580
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
kube-proxy extraArgs ignored #5505
Comments
Talos doesn't update the manifests automatically for safety reasons. You need to run |
Yes but I don't want to upgrade kubernetes version. Just add a parameter to the Can I run the |
| Can I run the upgrade-k8s with the actual version ? yes, you can do |
I just noticed you're on 0.14, but it already supports this flow: https://www.talos.dev/v0.14/guides/upgrading-kubernetes/ |
I think this is an actual (and ongoing!) issue- I'm running v1.2.2 with kubernetes 1.23.4 and am seeing the same problem. I've just run through MachineConfig:
Daemonset:
|
First of all, you can do Second, make sure you have update machine config on all control plane nodes for |
Ah! Thanks @smira - I see from a clarifying comment you made on #5959 that talos will never update the kube-proxy manifest! I haven't fully groked WHY kube-proxy isn't updated - especially since the manifests.kubernetes.talos.dev resource has the update, but I'll dig in more |
@smira It seems that running talos/pkg/cluster/kubernetes/daemonset.go Lines 104 to 109 in 49e9f80
|
I'm sorry, why would extraArgs need to be updated? |
Same reason as in the description of this issue, to change the metrics bind address |
This might be confusing, we'll get a fix for it. You can always update daemonset directly with |
Bug Report
kube-proxy pod runs without args specified in the machine configuration file with key
cluster.proxy.extraArgs
Description
To change the bind address of kube-proxy for metrics, I edit the configuration file of each node as it :
and then apply it with
talosctl apply-config -n 10.80.1.1 -f controlplane1.yaml
When I watch the pod, I see that the corresponding kube-proxy is restarted (but not recreated), and if I describe it, I see that its command line arguments did not change :
I tried to delete the pod; it was recreated but still with the same command line.
In fact the daemonset
kube-proxy
is not updated.When I changed the
cluster.scheduler.extraArgs
andcluster.controllerManager.extraArgs
the corresponding pods were successfully recreated with the new command.Environment
0.14.1
1.21.6
amd64
The text was updated successfully, but these errors were encountered: