when we create a cluster the control plane node should have a label node-role.kubernetes.io/control-plane= as weave-gitops-enterprise considers it ready when it has this label
➜ k get nodes
NAME STATUS ROLES AGE VERSION
ip-192-168-130-239.eu-north-1.compute.internal Ready <none> 16h v1.24.9-eks-49d8fe8
workaround after cluster is created
kubectl label nodes ip-192-168-130-239.eu-north-1.compute.internal node-role.kubernetes.io/control-plane=
Problem
- Checking control plane is ready by labels could be misleading as clusters in providers like AWS, GKE, .. don't give you access to
ControlPlane
Possible Solution
- To check control plane readiness by calling control plane API
- still searching for other solutions
when we create a cluster the control plane node should have a label
node-role.kubernetes.io/control-plane=as weave-gitops-enterprise considers it ready when it has this labelworkaround after cluster is createdkubectl label nodes ip-192-168-130-239.eu-north-1.compute.internal node-role.kubernetes.io/control-plane=Request feature for cluster bootstrap controller
Problem
ControlPlanePossible Solution