Cluster API
cluster-api.sigs.k8s.io
- Free plan
- Windows
- macOS
- Linux
- API
- Self-hosted
What Cluster API is
Cluster API is an open-source Kubernetes project for provisioning and operating multiple clusters through declarative APIs and tooling. Its lifecycle operations cover creating, scaling, upgrading, and destroying Kubernetes-conformant clusters. It is designed for on-premises and cloud environments, with interchangeable infrastructure providers and provider implementations for bootstrap, control plane, IPAM, addons, and runtime extensions. The ecosystem includes AWS, Azure, GCP, OpenStack, vSphere, and KubeVirt; kubeadm is the default bootstrap provider.
A management cluster can use clusterctl or the Cluster API Operator to manage provider components. Clusterctl fetches provider component YAML and installs it, while the Operator uses a declarative approach intended to support GitOps workflows. Getting started requires an existing Kubernetes cluster accessible through kubectl; kind, Docker, and Helm are common prerequisites. The clusterctl CLI has downloads for Linux, macOS, and Windows. Cluster API does not manage a single cluster spanning multiple infrastructure providers or clusters it did not provision. The project supports its latest two minor releases, with each release supported for roughly 12 months including maintenance. Its security guidance recommends auditing clusters, nodes, and cloud-provider activity and using least-privilege credentials.
Who it suits
Cluster API is aimed at platform operators managing Kubernetes cluster lifecycles across cloud or on-premises environments. It suits teams that can provide an existing management cluster and manage provider-specific responsibilities.
Good to know, and what to watch
- Declarative tooling covers cluster creation, scaling, upgrades, and deletion.
- Supports multiple infrastructure provider implementations.
- Includes clusterctl and Cluster API Operator management paths.
- Supports multi-cluster provisioning and upgrades.
- Project is open source and free.
- Requires an existing Kubernetes cluster accessible through kubectl.
- Does not manage clusters it did not provision.
- Cannot manage one cluster across multiple infrastructure providers.
- Provider implementations are maintained by their respective teams.
Plans
Every plan and priceCluster API
Open source
Getting started
- Open the Cluster API website
- Prepare an existing Kubernetes cluster accessible through kubectl
- Install kind, Docker, or Helm if needed as common prerequisites
- Choose clusterctl or the Cluster API Operator for provider management
- Install clusterctl on Linux, macOS, or Windows, or use Homebrew on macOS or Linux
- Use the management cluster to install provider components
Limits to check
The free Cluster API plan is open source, while infrastructure and provider component costs depend on the providers selected. The project does not manage clusters it did not provision or a single cluster spanning multiple infrastructure providers.
The verdict
Cluster API offers a provider-based way to manage multiple Kubernetes cluster lifecycles. Its scope excludes externally provisioned clusters and a single cluster spanning multiple providers, so provider documentation and production readiness need attention.
Questions people ask
How much does Cluster API cost?
The Cluster API plan is free. It is an open-source Kubernetes project; provider components and infrastructure costs depend on selected providers.
Which platforms are supported?
Cluster API lists API, Linux, macOS, self-hosted, and Windows platforms. Clusterctl downloads are documented for Linux, macOS, and Windows, with Homebrew installation for macOS and Linux.
What providers can it use?
The provider ecosystem includes infrastructure, bootstrap, control plane, IPAM, addon, and runtime extension providers. Listed environments include AWS, Azure, GCP, OpenStack, vSphere, KubeVirt, and many others.
What is required before installation?
You need an existing Kubernetes cluster that kubectl can access. The quick start also lists kind, Docker, and Helm as common prerequisites.
Does Cluster API manage any Kubernetes cluster?
It does not manage a single cluster spanning multiple infrastructure providers or clusters that it did not provision.
How is provider management installed?
The quick start offers clusterctl and the Cluster API Operator. Clusterctl fetches provider component YAML, while the Operator manages providers declaratively.
What the maker publishes
- Bootstrap and control plane
- The provider ecosystem includes bootstrap and control plane implementations, with kubeadm built in. source
- Community support
- The project directs users to the Kubernetes Slack #cluster-api channel, the SIG Cluster Lifecycle Google Group, and weekly working-group meetings for questions and project updates. source
- Downloads
- The clusterctl CLI has documented downloads for Linux, macOS, and Windows, plus Homebrew installation for macOS and Linux. source
- GitOps
- The Cluster API Operator uses a declarative approach to manage providers and aims to support day-to-day workflows with GitOps. source
- Infrastructure
- It is designed to work across on-premises and cloud environments and can be extended with infrastructure providers such as AWS, Azure, and vSphere. source
- Installation
- The quick start offers clusterctl and the Cluster API Operator as installation paths; clusterctl fetches provider component YAML and installs it. source
- Integrations
- The quick start lists infrastructure providers including AWS, Azure, GCP, OpenStack, vSphere, and KubeVirt, among others. source
- Intended users
- The project describes its automation as intended for platform operators managing Kubernetes cluster lifecycles. source
- Lifecycle
- Its stated goals include creating, scaling, upgrading, and destroying Kubernetes-conformant clusters through a declarative API. source
- Lifecycle operations
- Its stated goals include creating, scaling, upgrading, and destroying Kubernetes-conformant clusters through a declarative API. source
- Management tools
- The quick start describes clusterctl and the Cluster API Operator as two paths for managing provider components in a management cluster. source
- Notable limit
- The project states that Cluster API does not manage a single cluster spanning multiple infrastructure providers or clusters that it did not provision. source
- Prerequisites
- Using Cluster API requires an existing Kubernetes cluster accessible through kubectl; the quick start also lists kind, Docker, and Helm as common prerequisites. source
- Production guidance
- The quick start recommends using a production management cluster with backup and disaster recovery policies and says kind is not designed for production. source
- Provider ecosystem
- The project lists infrastructure, bootstrap, control plane, IPAM, addon, and runtime extension providers, including AWS, Azure, GCP, OpenStack, and vSphere. source
- Provider model
- The project supports interchangeable provider implementations, with kubeadm as the default bootstrap provider. source
- Provider support responsibility
- Each provider is maintained by its respective team, and the project recommends reviewing provider documentation and doing due diligence before production use. source
- Purpose
- Cluster API provides declarative APIs and tooling to provision, upgrade, and operate multiple Kubernetes clusters. source
- Security
- The project’s user security guidance recommends auditing management and workload clusters, nodes, and cloud-provider activity, and using least-privilege credentials. source
- Support channels
- The project directs users to the Kubernetes Slack #cluster-api channel, the SIG Cluster Lifecycle Google Group, and weekly working group sessions for questions and news. source
- Support policy
- The project actively supports its latest two minor releases, while each minor release is supported for roughly 12 months including a maintenance period. source
Checked against the maker's pages on 7 Oct 2026.