集群 API 提供商 Hetzner:rocket: 在 Hetzner 上管理 Kubernetes 集群的最佳方式,完全声明性、Kubernetes 原生且具有自愈能力
集群 API 提供商 Hetzner:rocket: 在 Hetzner 上管理 Kubernetes 集群的最佳方式,完全声明性、Kubernetes 原生且具有自愈能力
[!NOTE] The Cluster API Provider Hetzner is independently maintained by Syself and the community. It is not an official Hetzner project.
If you have any questions about this project, please start a conversation in the Discussions tab or contact us at [email protected].
The Cluster API Provider Hetzner (CAPH) provides a way to declaratively create and manage infrastructure on Hetzner, in a Kubernetes-native way. It extends the Kubernetes API with Custom Resource Definitions (CRDs) allowing you to interact with clusters in the same fashion you interact with workload.
Key benefits include:
CAPH enables you to have DIY Kubernetes on Hetzner at any scale, with full control over your infrastructure and clusters configuration.
If you want a batteries-included solution instead, you can try Syself free for 14 days.
Documentation can be found at caph.syself.com. You can contribute to it by modifying the contents of the /docs directory.
The best way to get started with CAPH is to spin up a cluster. For that you can follow our Managing Kubernetes on Hetzner with Cluster API article featured in the Hetzner Community Tutorials.
Additional resources from the documentation:
In addition to the pure creation and operation of Kubernetes clusters, this provider can also validate and approve certificate signing requests. This increases security as the kubelets of the nodes can be operated with signed certificates, and enables the metrics-server to run securely. Click here to read more about the CSR controller.
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.
Cluster API Provider Hetzner relies on a few prerequisites that must be already installed in the operating system images, such as a container runtime, kubelet, and kubeadm.
Reference images are available in kubernetes-sigs/image-builder.
If it's not possible to pre-install these prerequisites, custom scripts can be deployed through the kubeadm config.
In case you want a solution with managed node images, Syself might be interesting for you.
We, the maintainers and the community, welcome any contributions to Cluster API Provider Hetzner. Feel free to contact the maintainers for suggestions, contributions and help.
To set up your environment, refer to the development guide.
For new contributors, check out issues tagged as [good first issue][good_first_issue]. These are typically smaller in scope and great for getting familiar with the codebase.
We encourage all active community members to act as if they were maintainers, even without "official" write permissions. This is a collaborative effort serving the Kubernetes community.
If you have an active interest and you want to get involved, you have real power! Don't assume that the only people who can get things done around here are the "maintainers".
We would also love to add more "official" maintainers, so show us what you can do!
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.
If you think you have found a bug, please follow these steps:
We also use the issue tracker to track features. If you have an idea for a feature or think that you can help Cluster API Provider Hetzner become even more awesome, then follow these steps:
this and Cluster API Provider Hetzner does that".For more information about Syself, our platform, or any generall information about the Cluster API Provider Hetzner, feel free to reach out to us. Below are some ways to contact our team:
暂无开放 Issues，或尚未同步最近议题。