Invalid CCM yaml template

[jiejiecn]

I tried to setup an unmanaged k8s cluster on Linode through Rancher. After this I tried to install CCM so I can create a NodeBalancer through Serivce LoadBalancer. During the procedure, I found some invalid parameters in the template yaml file. Maybe it's not up to date.

Under the "DaemonSet" section:

  hostNetwork: true                                          #error log shows port 10260 already used on the node
                                                                         #just remove this hostNetwork, the pods can run normally
  containers:
      image: linode/linode-cloud-controller-manager:v0.4.19
      imagePullPolicy: Always
      name: ccm-linode
      args:
      - --leader-elect-resource-lock=endpoints    #error log shows this must be "leases"
      - --v=3
      - --port=0                                                      #error log shows this --port is an unknow arg
      - --secure-port=10253

Other issues:
The log shows I need to specify the --master or --kubeconfig, otherwise the CCM can't access the API server.
I mounted a volume with kubeconfig file and specify the --kubeconfig, it's working. But I don't think it's a good idea to do so.
I'm wondering if it's a BUG?

The final parameters that I make it running

I'm not specialized in k8s, pls correct me if I missed something :-)

[jiejiecn]

Update:
I add "automountServiceAccountToken: true" to automatically mount the kubeconfig in the pod and it can start without specify --kubeconfig

But the log shows:

error retrieving resource lock kube-system/cloud-controller-manager: leases.coordination.k8s.io "cloud-controller-manager" is forbidden: User "system:serviceaccount:kube-system:ccm-linode" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "kube-system"

[jiejiecn]

Update:

I grant all methods on "leases" under "coordination.k8s.io" for ClusterRole "ccm-linode-clusterrole". The error in the log stopped.

So maybe the yaml file missing some rights for "leases" under ClusterRole section.

[rahulait]

Hi @jiejiecn , thanks for reporting this issue. We had a script which was outdated as it wasn't used much. Our preferred installation method is helm. We have updated the script for now and fix is in #251

We would recommend using helm install to install CCM on a rke2 cluster.