This is a cache of https://docs.okd.io/latest/machine_management/cluster_api_machine_management/cluster-api-about.html. It is a snapshot of the page at 2024-11-23T18:59:16.286+0000.
About the Cluster <strong>api</strong> - Managing machines with the Cluster <strong>api</strong> | Machine management | OKD 4
  1. Documentation
×

About the Cluster api

Managing machines with the Cluster api is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

The Cluster api is an upstream project that is integrated into OKD as a Technology Preview for Amazon Web Services (AWS), Google Cloud Platform (GCP), and VMware vSphere.

Cluster api overview

You can use the Cluster api to create and manage compute machine sets and compute machines in your OKD cluster. This capability is in addition or an alternative to managing machines with the Machine api.

For OKD 4 clusters, you can use the Cluster api to perform node host provisioning management actions after the cluster installation finishes. This system enables an elastic, dynamic provisioning method on top of public or private cloud infrastructure.

With the Cluster api Technology Preview, you can create compute machines and compute machine sets on OKD clusters for supported providers. You can also explore the features that are enabled by this implementation that might not be available with the Machine api.

Cluster api benefits

By using the Cluster api, OKD users and developers gain the following advantages:

  • The option to use upstream community Cluster api infrastructure providers that might not be supported by the Machine api.

  • The opportunity to collaborate with third parties who maintain machine controllers for infrastructure providers.

  • The ability to use the same set of Kubernetes tools for infrastructure management in OKD.

  • The ability to create compute machine sets by using the Cluster api that support features that are not available with the Machine api.

Cluster api limitations

Using the Cluster api to manage machines is a Technology Preview feature and has the following limitations:

  • To use this feature, you must enable the TechPreviewNoUpgrade feature set.

    Enabling this feature set cannot be undone and prevents minor version updates.

  • Only Amazon Web Services (AWS), Google Cloud Platform (GCP), and VMware vSphere clusters can use the Cluster api.

  • You must manually create the primary resources that the Cluster api requires. For more information, see "Getting started with the Cluster api".

  • You cannot use the Cluster api to manage control plane machines.

  • Migration of existing compute machine sets created by the Machine api to Cluster api compute machine sets is not supported.

  • Full feature parity with the Machine api is not available.

  • For clusters that use the Cluster api, OpenShift CLI (oc) commands prioritize Cluster api objects over Machine api objects. This behavior impacts any oc command that acts upon any object that is represented in both the Cluster api and the Machine api.

    For more information and a workaround for this issue, see "Referencing the intended objects when using the CLI" in the troubleshooting content.

Additional resources

Cluster api architecture

The OKD integration of the upstream Cluster api is implemented and managed by the Cluster Capi Operator. The Cluster Capi Operator and its operands are provisioned in the openshift-cluster-api namespace, in contrast to the Machine api, which uses the openshift-machine-api namespace.

The Cluster Capi Operator

The Cluster Capi Operator is an OKD Operator that maintains the lifecycle of Cluster api resources. This Operator is responsible for all administrative tasks related to deploying the Cluster api project within an OKD cluster.

If a cluster is configured correctly to allow the use of the Cluster api, the Cluster Capi Operator installs the Cluster api components on the cluster.

For more information, see the "Cluster Capi Operator" entry in the Cluster Operators reference content.

Additional resources

Cluster api primary resources

The Cluster api consists of the following primary resources. For the Technology Preview of this feature, you must create these resources manually in the openshift-cluster-api namespace.

Cluster

A fundamental unit that represents a cluster that is managed by the Cluster api.

Infrastructure

A provider-specific resource that defines properties that are shared by all the compute machine sets in the cluster, such as the region and subnets.

Machine template

A provider-specific template that defines the properties of the machines that a compute machine set creates.

Machine set

A group of machines.

Compute machine sets are to machines as replica sets are to pods. To add machines or scale them down, change the replicas field on the compute machine set custom resource to meet your compute needs.

With the Cluster api, a compute machine set references a Cluster object and a provider-specific machine template.

Machine

A fundamental unit that describes the host for a node.

The Cluster api creates machines based on the configuration in the machine template.