Welcome to the official documentation for the Cluster API Provider Hetzner (CAPH). If you are new to it, you can keep reading the Getting Started section, the Quickstart guide will walk you through your first cluster setup.
CAPH is a Kubernetes Cluster API provider that facilitates the deployment and management of self-managed Kubernetes clusters on Hetzner infrastructure. The provider supports both cloud and bare-metal instances for consistent, scalable, and production-ready cluster operations.
It is recommended that you have at least a basic understanding of Cluster API before getting started with CAPH. You can refer to the Cluster API Quick Start Guide from its official documentation.
This provider's versions are compatible with the following versions of Cluster API:
| CAPI Version | Hetzner Provider v1.0.x | Hetzner Provider v1.1.x |
|---|---|---|
v1.8.x | ✅ | ❔ |
v1.9.x | ✅ | ❔ |
v1.10.x | ✅ | ✅ |
v1.11.x start of beta2 | ❌ | ✅ |
v1.12.x | ❌ | ✅ |
This provider's versions can install and manage the following versions of Kubernetes:
Hetzner Provider v1.0.x | Hetzner Provider v1.1.x | |
|---|---|---|
| Kubernetes 1.31.x | ✅ | ❌ |
| Kubernetes 1.32.x | ✅ | ✅ |
| Kubernetes 1.33.x | ✅ | ✅ |
| Kubernetes 1.34.x | ✅ | ✅ |
| Kubernetes 1.35.x | ❔ | ✅ |
Test status:
Related:
Compatibility notes:
v1.1.x still implements the deprecated v1beta1 contract. On CAPI v1.11.x through v1.15.x , this should keep working via the temporary compatibility layer for the deprecated v1beta1 contract, but upstream documents limitations and does not recommend staying on v1beta1 long term. That compatibility is planned to end when v1beta1 stops being served in CAPI v1.16.x . See the upstream version support page, the upstream v1.10 to v1.11 migration guide, the upstream InfraMachine contract notes, and the upstream removal plan.v1.2.x will be the v1beta2 line and aligns with CAPI v1.11.x and later v1beta2 releases.Each version of Cluster API for Hetzner will attempt to support at least two Kubernetes versions.
NOTE: As the versioning for this project is tied to the versioning of Cluster API, future modifications to this policy may be made to more closely align with other providers in the Cluster API ecosystem.
As the versioning for this project is tied to the versioning of Cluster API, future modifications to this policy may be made to more closely align with other providers in the Cluster API ecosystem.