Sanitation ops configures kubelets and admin kubeconfigs after building an HA control plane. Where should they point API clients?
Select an answer to reveal the explanation.
Short Explanation
Give everyone the published City Hall number—the VIP—not Bob’s desk phone that vanishes when Bob’s on vacation. Workers and kubeconfigs should use controlPlaneEndpoint so losing one control-plane host doesn’t mean rewriting every node. Hard-coding one IP quietly undoes your HA work.
Full Explanation
After HA bootstrap, kubelets and kubectl contexts should target the load-balanced controlPlaneEndpoint. Pinning clients to one control-plane IP recreates a SPOF and breaks when that node is down for maintenance. The VIP/DNS name remains valid as members change.