-
Hello, Now project decided to get rid of windows nodes. And we want to simplify talos cluster deployment and return kube-proxy control to Talos by setting: proxy = {
disabled = false
extraArgs = {
metrics-bind-address = "0.0.0.0:10249"
}
} But I'm really confused and don't know how to proceed with migration procedure. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
you can just delete custom kube-proxy manifests from api server and run a |
Beta Was this translation helpful? Give feedback.
-
I don't think you can run two kube-proxy daemons on the same machine. But also stopping kube-proxy won't kill existing connections, it will stop reconciliation (creating/removing iptables rules). So probably I would nuke your own daemonset, and re-enable kube-proxy on Talos side, Talos will immediately re-create the daemonset. |
Beta Was this translation helpful? Give feedback.
you can just delete custom kube-proxy manifests from api server and run a
talosctl upgrade-k8s
(upgrading to same k8s version, can do--dry-run
to see the changes) after re-enabling kube-proxy in machine config.