`selector` is the label selector in string format to avoid Is equal to the number of non-terminated control plane machines Of the control plane is able to transition to ready. Total number of non-terminated control plane instances, Is equal to the number of fully running and ready control plane machines Total number of fully running and ready control plane instances. High availability control planes, then the status object must have the Where the ImplementationControlPlane has a concept of replicas, e.g. Required status fields for implementations using replicas Ready denotes that the target API Server is ready to receive requests. Transitions to initialized when the controller detects that kubeadm has uploadedĪ kubeadm-config configmap, which occurs at the end of kubeadm provisioning. Target's control plane has been contactable. Implementation in Kubeadm Control Plane ControllerĪ boolean field that is true when the target cluster hasĬompleted initialization such that at least once, the The status object must have the following fields defined: Field The ImplementationControlPlane object must have a status object. A duration of 0 will retry deletion indefinitely. Will attempt to delete the Node that is hosted by a Machine after the Machine is marked forĭeletion. MachineTemplate.nodeDeletionTimeout - is a *metav1.Duration defining how long the controller The default value is 0, meaning that the node can be drained without any time limitations. That the controller will spend on draining a control plane node. MachineTemplate.nodeDrainTimeout - is a *metav1.Duration defining the total amount of time The namespace in the ObjectReference mustīe in the same namespace of the control plane object. MachineTemplate.infrastructureRef - is a corev1.ObjectReference to a custom resource is a map of string keys and values containingĪrbitrary metadata to be applied to control plane machines. To organize and categorize control plane machines. is a map of string keys and values that can be used tadata - is a struct containing info about metadata for control plane MachineTemplate - is a struct containing details of the control plane Required spec fields for implementations using Machines The value must be a valid semantic version Īlso if the value provided by the user does not start with the v prefix, it version - is a string representing the Kubernetes version to be usedīy the control plane machines.Required spec fields for implementations using version More information about the scale subresource can be found in the Kubernetesĭocumentation. Scale subresource with the following signature: In the KubeadmControlPlane, this represents the desired Replicas - is an integer representing the number of desired CRD contracts Required spec fields for implementations using replicas ntrolplaneEndpoint in its parent Cluster object. The ImplementationControlPlane must rely on the existence of The Cluster controller bubbles up status.ready into ntrolPlaneReady and status.initialized into a controlPlaneInitialized condition from the Control Plane CR. The Control Plane controller should normally take no action during reconciliation until it sees the ownerReference.Ī Control Plane controller implementation should exit reconciliation until it sees populated. The Cluster controller will set an OwnerReference on the Control Plane. CNI - should be left to user to apply once control plane is instantiated.Kubernetes control plane consisting of the following services: Required Control Plane Services The general expectation of a control plane controller is to instantiate a We refer to an example ImplementationControlPlane where not otherwise specified. Kubeadm control plane controller ( KubeadmControlPlane). Create/manage a secret with the kubeconfig file for accessing the workload cluster.Ī reference implementation is managed within the core Cluster API project as the.Provide information about the state of the control plane to downstream.Managing a set of machines that represent a Kubernetes control plane.

The Control Plane controller’s main responsibilities are:

Implementing Topology Mutation Hook Extensions Updating Machine Infrastructure and Bootstrap Templates Upgrading management and workload clusters

Controlplane