cis-operator doesn't support Kubernetes cluster managed by Scaleway

[nbisson]

Hi,
cis-operator works only with providers declared here : https://github.com/rancher/kubernetes-provider-detector/tree/master/providers
Having a Kubernetes cluster managed by Scaleway, my cluster can't launch cis-operator. When executing, getting this error :

time="2021-07-23T09:33:28Z" level=info msg="Starting CIS-Operator"
time="2021-07-23T09:33:29Z" level=fatal msg="Error building controller: unknown provider"

Shouldn't the start be allowed even if the detection of the provider fails ?

Thank's.

[xom4ek]

Any news about this issue?

[xom4ek]

Found easy way for start cis-operator - just add label to any node in cluster

k label node MYNODE kubernetes.azure.com/cluster=""

Operator start think about this cluster "aks here" but its not a problem for start scaning and configuration profiles

[manicole]

Same here using OVHCloud managed Kubernetes cluster. Thanks for the trick @xom4ek !

[Raph0773]

Hi @manicole !

What label did you put on OVH nodes ?

Thanks !

[belaw]

I'm getting this problem on a self hosted cluster (kubespray)

[c-romeo]

I'm getting this problem on a self hosted cluster (kubespray)

Hi @belaw! just applying @xom4ek fix solved the issue

k label node MYNODE kubernetes.azure.com/cluster=""

[belaw]

I'm getting this problem on a self hosted cluster (kubespray)

Hi @belaw! just applying @xom4ek fix solved the issue

k label node MYNODE kubernetes.azure.com/cluster=""

Hi @c-romeo, thanks, I should have mentioned that I already figured that out 😁 and I just wanted to push this issue because the node label makes the cluster look like a cloud based cluster when you view it in Rancher.

[ronhorton]

The question on this one is, "do we want to implement a programatic version of the work around so that the operator doesn't fail when provider is unknown?"
this issue was release noted (i'm verifying the veracity of that statement ;) ), and the workaround noted resolves the issue. #103 (comment)