What is the purpose of the cluster.controlPlane.endpoint field in the controlplane.yaml? #9824
-
I am trying to understand the purpose of the cluster.controlPlane.endpoint field in the controlplane.yaml. # within the controlplane.yaml
cluster:
controlPlane:
endpoint: https://<my-adress>:6443 As I was trying to figure out which one of my addresses I should put in there I was asking myself what this is for in the first place. To allow all the addresses for TLS I can add them to the certSANs fields. Using 127.0.0.1 as endpoint seems to make no difference. Using an invalid IP address seems to work, too. I get some warnings like the following from the kernel for an invalid endpoint, but the rest seems to work.
What is the purpose of providing a public entrypoint address here? What feature will be missing when this is wrongly configured? Any help is appreciated. :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The answer depends on the way you have your cluster configured (mostly if you disable some default features), but roughly it's the following:
So in general, Talos by default would operate just fine if you make it invalid, but it might affect cluster stability recovery under tough circumstances (e.g. if cluster discovery becomes unavailable). Make sure the endpoint is something that other nodes in the cluster can reach the controlplane at the very least. In a single-node scenario, none of the above matters except for certSANs. |
Beta Was this translation helpful? Give feedback.
The answer depends on the way you have your cluster configured (mostly if you disable some default features), but roughly it's the following:
kubeconfig
file you receive withtalosctl kubeconfig
So in ge…