Skip to content

kubernetes-sigs/cluster-api

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Folders and files

NameName
Last commit message
Last commit date
Aug 19, 2024
Aug 16, 2024
Jul 18, 2024
Aug 22, 2024
Aug 15, 2024
Aug 15, 2024
Jul 26, 2024
Aug 15, 2024
Mar 1, 2023
Aug 22, 2024
Mar 18, 2024
Aug 15, 2024
Mar 26, 2024
Aug 22, 2024
Aug 15, 2024
Sep 30, 2020
Aug 22, 2024
Aug 23, 2024
Jul 25, 2024
Jun 10, 2022
Jun 27, 2024
Apr 18, 2023
Aug 16, 2022
Aug 14, 2023
Aug 15, 2024
May 6, 2024
Aug 14, 2024
Sep 17, 2022
Apr 15, 2018
Aug 22, 2024
Jan 24, 2024
May 17, 2024
Apr 29, 2024
May 25, 2023
Apr 19, 2021
Aug 22, 2024
Apr 17, 2024
Apr 17, 2024
Dec 20, 2017
Aug 22, 2024
Aug 22, 2024
Jul 25, 2024
Aug 15, 2024
Jun 10, 2024

Repository files navigation

capi

GitHub release (latest SemVer)

Cluster API

👋 Welcome to our project! Our Book can help you get started and provides lots of in-depth information.

Useful links

✨ What is the Cluster API?

Cluster API is a Kubernetes subproject focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters.

Started by the Kubernetes Special Interest Group (SIG) Cluster Lifecycle, the Cluster API project uses Kubernetes-style APIs and patterns to automate cluster lifecycle management for platform operators. The supporting infrastructure, like virtual machines, networks, load balancers, and VPCs, as well as the Kubernetes cluster configuration are all defined in the same way that application developers operate deploying and managing their workloads. This enables consistent and repeatable cluster deployments across a wide variety of infrastructure environments.

⚙️ Providers

Cluster API can be extended to support any infrastructure (AWS, Azure, vSphere, etc.), bootstrap or control plane (kubeadm is built-in) provider. There is a growing list of supported providers available.

🤗 Community, discussion, contribution, and support

Cluster API is developed in the open, and is constantly being improved by our users, contributors, and maintainers. It is because of you that we are able to automate cluster lifecycle management for the community. Join us!

If you have questions or want to get the latest project news, you can connect with us in the following ways:

  • Chat with us on the Kubernetes Slack in the #cluster-api channel
  • Subscribe to the SIG Cluster Lifecycle Google Group for access to documents and calendars
  • Join our Cluster API working group sessions where we share the latest project news, demos, answer questions, and triage issues

Pull Requests and feedback on issues are very welcome! See the issue tracker if you're unsure where to start, especially the Good first issue and Help wanted tags, and also feel free to reach out to discuss.

See also our contributor guide and the Kubernetes community page for more details on how to get involved.

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.