All Projects → kubernetes-sigs → Cluster Api

kubernetes-sigs / Cluster Api

Licence: apache-2.0
Home for Cluster API, a subproject of sig-cluster-lifecycle

Programming Languages

go
31211 projects - #10 most used programming language

Projects that are alternatives of or similar to Cluster Api

cluster-api-provider-hcloud
Cluster API infrastructure provider for Hetzner's Hcloud
Stars: ✭ 26 (-98.69%)
Mutual labels:  k8s-sig-cluster-lifecycle
image-builder
Cross provider Kubernetes image building utility.
Stars: ✭ 187 (-90.61%)
Mutual labels:  k8s-sig-cluster-lifecycle
cluster-api-provider-digitalocean
The DigitalOcean provider implementation of the Cluster Management API
Stars: ✭ 85 (-95.73%)
Mutual labels:  k8s-sig-cluster-lifecycle
bootkube
This project now lives at https://github.com/kinvolk/bootkube
Stars: ✭ 1,168 (-41.37%)
Mutual labels:  k8s-sig-cluster-lifecycle
cluster-api-provider-openstack
cluster-api-openstack.sigs.k8s.io/
Stars: ✭ 187 (-90.61%)
Mutual labels:  k8s-sig-cluster-lifecycle
system-validators
A set of system-oriented validators for kubeadm preflight checks.
Stars: ✭ 22 (-98.9%)
Mutual labels:  k8s-sig-cluster-lifecycle
cluster-api-provider-ibmcloud
Cluster API Provider for IBM Cloud
Stars: ✭ 46 (-97.69%)
Mutual labels:  k8s-sig-cluster-lifecycle
cluster-api-provider-nested
Cluster API Provider for Nested Clusters
Stars: ✭ 240 (-87.95%)
Mutual labels:  k8s-sig-cluster-lifecycle
cluster-api-provider-docker
A Cluster API Provider implementation using docker containers as the infra provider. Cluster API locally for a change!
Stars: ✭ 51 (-97.44%)
Mutual labels:  k8s-sig-cluster-lifecycle
Kubespray
Deploy a Production Ready Kubernetes Cluster
Stars: ✭ 11,588 (+481.73%)
Mutual labels:  k8s-sig-cluster-lifecycle

capi

Build Status

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 sub-project 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
  • Participate in the conversations on Kubernetes Discuss
  • 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.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].