XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Feedback: XO Cloud Controller Manager (CCM)

    Scheduled Pinned Locked Moved Infrastructure as Code
    1 Posts 1 Posters 5 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T Offline
      ThasianXi
      last edited by

      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

      Rancher_XO_CCM_labels.png

      OCNE_XO-CCM_pod.png

      1 Reply Last reply Reply Quote 0
      • First post
        Last post