Replies: 1 comment 2 replies
-
Are you referring to the hetzner CCM? The k3s embedded CCM doesn't rely on this label for anything. If you're fighting with the hetzner cloud provider, you might consider opening an issue on their repo, instead of here? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem? Please describe.
I'm trying to set up wireguard to protect all the communications between my k8s nodes.
I want that to include the initialization steps as well (the script from https://get.k3s.io), so the flannel CNI cannot address this.
I'm doing this in the hetzner cloud, where I cannot use the hetzner private network because it doesn't support connections between different regions and I'm aiming for global coverage.
The problem is that if I set node-ip to the desired private ip, the CCM fails because it won't be able to identify the node by the "alpha.kubernetes.io/provided-node-ip" label. Furthermore, this label is not allowed to be initialized on the kubelet startup, so I cannot change it.
Describe the solution you'd like
It would be ideal to separate the two uses of node-ip and add control to manage them separately:
I'm also open for alternative suggestions, but I couldn't figure out any.
Beta Was this translation helpful? Give feedback.
All reactions