Fix CloudDualStackNodeIPs feature-gate inconsistency

[brandond]

Proposed Changes

Fix CloudDualStackNodeIPs feature-gate inconsistency

Enable the feature-gate for both kubelet and cloud-controller-manager. Enabling it on only one side breaks RKE2, where feature-gates are not shared due to kubelet and ccm running in different processes.

Fixes RKE2 regression introduced by #8581

Types of Changes

bugfix

Verification

See linked issue

Testing

Linked Issues

• CloudDualStackNodeIPs feature-gate not consistently enabled #8666

User-Facing Change

Further Comments

[manuelbuil]

To fix the kubeflag test you should modify https://github.com/k3s-io/k3s/blob/master/tests/integration/kubeflags/kubeflags_test.go#L151-L156 because now the cloud-controller includes --feature-gates=CloudDualStackNodeIPs=true. This is the log it should search for:

"Running cloud-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --authorization-kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --bind-address=127.0.0.1 --cloud-config=/var/lib/rancher/k3s/server/etc/cloud-config.yaml --cloud-provider=k3s --cluster-cidr=10.42.0.0/16 --configure-cloud-routes=false --controllers=*,-route,-cloud-node,-cloud-node-lifecycle --feature-gates=CloudDualStackNodeIPs=true --kubeconfig=/var/lib/rancher/k3s/server/cred/cloud-controller.kubeconfig --leader-elect-resource-name=k3s-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false --secure-port=0"