Replies: 1 comment
-
It is correct that it's no the OS responsibility to set the external IP field for the Kubernetes You can set it manually or by implementing a controller manager of some sorts, but Talos Linux itself doesn't know about public/private IPs except for specific platforms (e.g. AWS, GCP, ...). KubeSpan acts on machine IPs, so it doesn't care about Kubernetes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am testing Talos+Omni+Kubespan out and one question I haven't figured out yet is how do you appropriately set the external/public ip for a node?
For example, I have 5 nodes inside a private network and no direct public ip. These show up correctly. I also have one more node that is running on a public vps that only has a single ipv4, no private/internal ips at all. This shows the public ip as the internal ip and nothing for the public ip.
I saw a talos FAQ which suggested it's the responsibility of the cloud controller manager. The VPS I'm using does not have any sort of cloud metadata service/etc. I also have several bare metal servers that will be in a similar situation. I installed https://github.com/siderolabs/talos-cloud-controller-manager thinking it may help, but wasn't sure what to actually configure with it. The public ip didn't seem to be editable.
Also with kubespan, should the internal ip end up being the kubespan ip for the node?
Beta Was this translation helpful? Give feedback.
All reactions