Feedback: XO Cloud Controller Manager (CCM)

ThasianXi

Offering feedback that my implementation of the XO CCM (v1.0.0-rc.1) into my K8s cluster was successful; I validated that the nodes were labeled as expected. I attached screenshots from Rancher and the CLI.
In my lab, I use OCNE 1.9 (Oracle Cloud Native Environment) on Oracle Linux 9.7.

In my setup, I edited the kubeadm-config ConfigMap and on all nodes added the Kubelet argument for the cloud provider.
I restarted the Kubelet on all nodes and then deployed the CCM via Method 1 per the documentation

From my setup to set the cloud-provider:

kubectl edit cm kubeadm-config -n kube-system

apiServer:
  extraArgs:
    cloud-provider: external
controllerManager:
  extraArgs:
    cloud-provider: external

sudo vim /etc/sysconfig/kubelet

KUBELET_EXTRA_ARGS="--fail-swap-on=false --cloud-provider=external"

sudo systemctl daemon-reload && sudo systemctl restart kubelet

nathanael-h

@ThasianXi Thank you very much for this detailed feedback! Did you deployed the CCM on a new cluster or an existing? My question is to know if you relied on the CCM to initialize the nodes.

Cyrille

@ThasianXi Thank you for your feedback !