https://rancher.com/ logo
s

silly-jordan-81965

05/18/2022, 11:15 AM
Hi we are noticing interesting behaviour when applying Cloud Provider config with Terraform for RKE2 clusters. We have the following config:
Copy code
rke_config { 
    machine_selector_config {
      config = {
        cloud-provider-name = "external"
        cloud-provider-config = file("occm/values.yaml")        
      }
    }
And in the value file:
Copy code
cloud_provider:
  name: openstack
  openstackCloudProvider:
    global:
      auth-url: <https://openstack.xxxxxx.io:5000/v3>
      tenant-id: someid 
      domain-id: default
      username: xxxxxxxx
      password: xxxxxxx
      region: region-name
However when we use this we see that the cluster node comes up but gets tainted with
<http://node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule|node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule>
Which gives the effect that neither cluster-agent nor coreDNS is up and running. What are we missing here?
👍 1
a

adventurous-battery-36116

05/23/2022, 1:45 AM
Try adding this to your machine selector config to disable the built-in RKE2 cloud controller:
disable-cloud-controller = true
👍🏻 1
s

silly-jordan-81965

05/30/2022, 2:17 PM
Thanks for the answer @adventurous-battery-36116.
36 Views