You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here you can find the official K3s documentation on this topic. Just as a note, while our cloud controller manager works with K3s, we don’t directly support K3s itself, as this question seems more specific to K3s than to our product.
In general, this looks good to me. As described in the kubelet cli reference, the value should be set to external, if you are running a external cloud controller manager, like ours.
You should be fine by setting --k3s-extra-args="--kubelet-arg=cloud-provider=external"
I would not worry to much about the unofficial support from hetzner for k3s. They are also using k3s for integration tests. See here how they use terraform to setup a k3s cluster:
I have the following set up for the control planes:
The first etcd server:
And the following when joining additional servers
And here is the equivalent script when joining worker nodes to the cluster:
I just want to be sure if this way of setting the cloud provider external flag is correct in k3s?
The text was updated successfully, but these errors were encountered: