Closed amimof closed 4 months ago
Earlier, a team member indicated that IPVS support is quasi deprecated: https://github.com/siderolabs/talos/issues/8332.
Talos Linux never updates/removes bootstrap manifests (including kube-proxy
) automatically, as it is considered to be dangerous.
You can still re-apply the manifests by doing a no-op talosctl upgrade-k8s --to <same-version>
.
Bug Report
After contralplane/node provisioning and cluster bootstrapping, changing kube-proxy proxy mode to
ipvs
will not actually apply the change to kube-proxy. The mode remains iniptables
proxy mode. Not sure if this behavior is intended or a bug.Description
I have a cluster that consists of 3 bare metal nodes. After I provisioned the nodes and bootstrapped the cluster I wanted to update the cluster, setting the proxy mode to
ipvs
.Then I applied the configuration with
talosctl apply-config -n talos-node1 -f controlplane.yaml -p @talos-node1.yaml
. However the changes do not seem to take affect. For example I can see that the kube-proxy is still iniptables
mode here:And also the same is true in the kube-proxy daemonset:
Only when I update the daemonset, manually setting
--proxy-mode=ipvs
will kube-proxy be configured with packet forwarding using ipvs.talos-node1.yaml
:controlplane.yaml
:Logs
Environment
talosctl version --nodes <problematic nodes>
]kubectl version --short
]