The process for getting started with control plane machine sets depends on the state of the ControlPlaneMachineSet custom resource (CR) in your cluster.
- Clusters with an active generated CR
-
Clusters that have a generated CR with an active state use the control plane machine set by default. No administrator action is required.
- Clusters with an inactive generated CR
-
For clusters that include an inactive generated CR, you must review the CR configuration and activate the CR.
- Clusters without a generated CR
-
For clusters that do not include a generated CR, you must create and activate a CR with the appropriate configuration for your cluster.
If you are uncertain about the state of the ControlPlaneMachineSet CR in your cluster, you can verify the CR status.
In {product-title} {product-version}, the control plane machine set is supported for Amazon Web Services (AWS), Google Cloud Platform (GCP), Microsoft Azure, Nutanix, and VMware vSphere clusters.
The status of the control plane machine set after installation depends on your cloud provider and the version of {product-title} that you installed on your cluster.
| Cloud provider | Active by default | Generated CR | Manual CR required |
|---|---|---|---|
{aws-first} |
X [1] |
X |
|
{gcp-first} |
X [2] |
X |
|
{azure-first} |
X [2] |
X |
|
Nutanix |
X [3] |
X |
|
{rh-openstack-first} |
X [3] |
X |
|
{vmw-full} |
X [4] |
X |
-
{aws-short} clusters that are upgraded from version 4.11 or earlier require CR activation.
-
{gcp-short} and {azure-short} clusters that are upgraded from version 4.12 or earlier require CR activation.
-
Nutanix and {rh-openstack} clusters that are upgraded from version 4.13 or earlier require CR activation.
-
{vmw-short} clusters that are upgraded from version 4.15 or earlier require CR activation.