Allow multi control plane clusters by knowing which node is the api server #7461
Labels
co/multinode
Issues related to multinode clusters
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Right now we assume if a node is a control plane it's automatically is the api server, and that's not necessarily the case so we need to make sure the api server node is explicitly specified.
The text was updated successfully, but these errors were encountered: