[release-1.27] Validate kube-cloud-controller-manager-arg new arg pulled in from k3s

[rancher-max]

Backport #4947

[fmoral2]

Validated on Version:

-$ rke2 version v1.27.7-rc2+rke2r1 (5fdc8d79f890391e6ce3485a5b92fa4925398210)

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"

Cluster Configuration:
2 node servers

Steps to validate the fix

1. Install rke2 with cloud controller manager args
2. Validate if applied
3. Check the logs
4. Validate nodes and pods are up and ok

Validation Results:

$ rke2 -v

rke2 version v1.27.7-rc2+rke2r1 (5fdc8d79f890391e6ce3485a5b92fa4925398210)
go version go1.20.10 X:boringcrypto

$ cat /etc/rancher/rke2/config.yaml
write-kubeconfig-mode: "0644"
tls-san:
  - fake.fqdn.value
node-name: ip-172-31-15-209.us-east-2.compute.internal
kube-cloud-controller-manager-arg:
  - allocate-node-cidrs=true
  - authentication-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - authorization-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - bind-address=127.0.0.1
  - cloud-config=/var/lib/rancher/rke2/server/etc/cloud-config.yaml
  - cloud-provider=rke2
  - cluster-cidr=10.42.0.0/24
  - configure-cloud-routes=true
  - controllers=*,-route,-service
  - feature-gates=CloudDualStackNodeIPs=true
  - kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - leader-elect-resource-name=rke2-cloud-controller-manager
node-external-ip: 52.14.84.120


$ sudo journalctl -xeu rke2-server.service | grep 'Running cloud'

Oct 25 15:43:25 ip-172-31-15-209 rke2[1770]: time="2023-10-25T15:43:25Z" level=info msg="Running cloud-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --authorization-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --bind-address=127.0.0.1 --cloud-config=/var/lib/rancher/rke2/server/etc/cloud-config.yaml --cloud-provider=rke2 --cluster-cidr=10.42.0.0/24 --configure-cloud-routes=true --controllers=*,-route,-service --feature-gates=CloudDualStackNodeIPs=true --kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --leader-elect-resource-name=rke2-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false" 




$ k get nodes 
NAME                                          STATUS     ROLES                       AGE     VERSION
ip-172-31-13-29.us-east-2.compute.internal    Ready   <none>                      24s     v1.27.7+rke2r1
ip-172-31-15-209.us-east-2.compute.internal   Ready      control-plane,etcd,master   6m54s   v1.27.7+rke2r1

[fmoral2]

Validated on Version:

-$ rke2 version v1.27.7-rc2+rke2r1 (5fdc8d79f890391e6ce3485a5b92fa4925398210)

Environment Details

Infrastructure
Cloud EC2 instance

Node(s) CPU architecture, OS, and Version:
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"

Cluster Configuration:
2 node servers

Steps to validate the fix

1. Install rke2 with cloud controller manager args
2. Validate if applied
3. Check the logs
4. Validate nodes and pods are up and ok

Validation Results:

$ rke2 -v

rke2 version v1.27.7-rc2+rke2r1 (5fdc8d79f890391e6ce3485a5b92fa4925398210)
go version go1.20.10 X:boringcrypto

$ cat /etc/rancher/rke2/config.yaml
write-kubeconfig-mode: "0644"
tls-san:
  - fake.fqdn.value
node-name: ip-172-31-15-209.us-east-2.compute.internal
kube-cloud-controller-manager-arg:
  - allocate-node-cidrs=true
  - authentication-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - authorization-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - bind-address=127.0.0.1
  - cloud-config=/var/lib/rancher/rke2/server/etc/cloud-config.yaml
  - cloud-provider=rke2
  - cluster-cidr=10.42.0.0/24
  - configure-cloud-routes=true
  - controllers=*,-route,-service
  - feature-gates=CloudDualStackNodeIPs=true
  - kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig
  - leader-elect-resource-name=rke2-cloud-controller-manager
node-external-ip: 52.14.84.120


$ sudo journalctl -xeu rke2-server.service | grep 'Running cloud'

Oct 25 15:43:25 ip-172-31-15-209 rke2[1770]: time="2023-10-25T15:43:25Z" level=info msg="Running cloud-controller-manager --allocate-node-cidrs=true --authentication-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --authorization-kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --bind-address=127.0.0.1 --cloud-config=/var/lib/rancher/rke2/server/etc/cloud-config.yaml --cloud-provider=rke2 --cluster-cidr=10.42.0.0/24 --configure-cloud-routes=true --controllers=*,-route,-service --feature-gates=CloudDualStackNodeIPs=true --kubeconfig=/var/lib/rancher/rke2/server/cred/cloud-controller.kubeconfig --leader-elect-resource-name=rke2-cloud-controller-manager --node-status-update-frequency=1m0s --profiling=false" 




$ k get nodes 
NAME                                          STATUS     ROLES                       AGE     VERSION
ip-172-31-13-29.us-east-2.compute.internal    Ready   <none>                      24s     v1.27.7+rke2r1
ip-172-31-15-209.us-east-2.compute.internal   Ready      control-plane,etcd,master   6m54s   v1.27.7+rke2r1