Kubernetes-native declarative infrastructure for OpenStack.
The Cluster API brings declarative, Kubernetes-style APIs to cluster creation, configuration and management.
The API itself is shared across multiple cloud providers allowing for true OpenStack hybrid deployments of Kubernetes. It is built atop the lessons learned from previous cluster managers such as kops and kubicorn.
- Check out the Cluster API Quick Start to create your first Kubernetes cluster on OpenStack using Cluster API. If you wish to use the external cloud provider, check out the External Cloud Provider as well.
- Native Kubernetes manifests and API
- Choice of Linux distribution (as long as a current cloud-init is available)
- Support for single and multi-node control plane clusters
- Deploy clusters with and without LBaaS available (only cluster with LBaaS can be upgraded)
- Support for security groups
- cloud-init based nodes bootstrapping
This provider's versions are compatible with the following versions of Cluster API:
| v1alpha3 (v0.3) | v1alpha4 (v0.4) | v1beta1 (v1.x) | |
|---|---|---|---|
| OpenStack Provider v1alpha3 (v0.3) | ✓ | ||
| OpenStack Provider v1alpha4 (v0.4) | ✓ | ||
| OpenStack Provider v1alpha4 (v0.5) | ✓ | ||
| OpenStack Provider v1alpha5 (v0.6) | ✓ | ||
| OpenStack Provider v1alpha6 | ✓ |
This provider's versions are able to install and manage the following versions of Kubernetes:
| v1.16 | v1.17 | v1.18 | v1.19 | v1.20 | v1.21 | v1.22 | v1.23 | v1.24 | v1.25 | |
|---|---|---|---|---|---|---|---|---|---|---|
| OpenStack Provider v1alpha3 (v0.3) | ✓ | ✓ | ✓ | ✓ | ✓ | |||||
| OpenStack Provider v1alpha4 (v0.4) | ✓ | |||||||||
| OpenStack Provider v1alpha4 (v0.5) | ✓ | ✓ | + | + | + | + | ||||
| OpenStack Provider v1alpha5 (v0.6) | ✓ | + | ✓ | ✓ | ✓ | |||||
| OpenStack Provider v1alpha6 | ✓ | + | ✓ | ✓ | ✓ |
This provider's versions are able to install Kubernetes to the following versions of OpenStack:
| Pike | Queens | Rocky | Stein | Train | Ussuri | Victoria | Wallaby | Xena | Yoga | |
|---|---|---|---|---|---|---|---|---|---|---|
| OpenStack Provider v1alpha3 (v0.3) | + | + | + | ✓ | ✓ | ✓ | ✓ | |||
| OpenStack Provider v1alpha4 (v0.4) | + | + | + | + | + | + | ✓ | |||
| OpenStack Provider v1alpha4 (v0.5) | + | + | + | + | + | + | ✓ | |||
| OpenStack Provider v1alpha5 (v0.6) | + | + | + | + | + | + | ✓ | ✓ | ✓ | ✓ |
| OpenStack Provider v1alpha6 | + | + | + | + | + | + | ✓ | ✓ | ✓ | ✓ |
Test status:
✓tested+should work, but we weren't able to test it
Each version of Cluster API for OpenStack will attempt to support 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 aligned with other providers in the Cluster API ecosystem.
NOTE: The minimum microversion of CAPI using nova is 2.53 now due to server tags support, see code for additional information.
NOTE: We require Keystone v3 for authentication.
ClusterAPI provider OpenStack images and manifests are published after every PR merge and once every day:
- With a Google Cloud account you can get a quick overview here
- The manifests are available under:
- master/infrastructure-components.yaml: latest build from the main branch, overwritten after every merge
- e.g. nightly_master_20210407/infrastructure-components.yaml: build of the main branch from 7th April
These artifacts are published via Prow and Google Cloud Build. The corresponding job definitions can be found here.
Note: Cluster API Provider OpenStack relies on a few prerequisites which have to be already installed in the used operating system images, e.g. a container runtime, kubelet, kubeadm,.. . Reference images can be found in kubernetes-sigs/image-builder. If it isn't possible to pre-install those prerequisites in the image, you can always deploy and execute some custom scripts through the KubeadmConfig.
Please see our book for in-depth documentation.
Are you interested in contributing to cluster-api-provider-openstack? We, the maintainers and community, would love your suggestions, contributions, and help! Also, the maintainers can be contacted at any time to learn more about how to get involved:
- via the cluster-api-openstack channel on Kubernetes Slack
- via the SIG-Cluster-Lifecycle Mailing List.
- during our Office Hours
- bi-weekly on Wednesdays @ 14:00 UTC on Zoom (link in meeting notes)
- Previous meetings: [ notes | recordings ]
In the interest of getting more new people involved we try to tag issues with
good first issue.
These are typically issues that have smaller scope but are good ways to start
to get acquainted with the codebase.
We also encourage ALL active community participants to act as if they are maintainers, even if you don't have "official" write permissions. This is a community effort, we are here to serve 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 also would love to add more "official" maintainers, so show us what you can do!
This repository uses the Kubernetes bots. See a full list of the commands here. Please also refer to the Contribution Guide and the Development Guide for this project.
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.
If you think you have found a bug please follow the instructions below.
- Please spend a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
- Get the logs from the cluster controllers. Please paste this into your issue.
- Open a new issue.
- Remember that users might be searching for your issue in the future, so please give it a meaningful title to help others.
- Feel free to reach out to the Cluster API community on the Kubernetes Slack.
We also use the issue tracker to track features. If you have an idea for a feature, or think you can help Cluster API Provider OpenStack become even more awesome follow the steps below.
- Open a new issue.
- Remember that users might be searching for your issue in the future, so please give it a meaningful title to help others.
- Clearly define the use case, using concrete examples.
- Some of our larger features will require some design. If you would like to include a technical design for your feature, please include it in the issue.
- After the new feature is well understood, and the design agreed upon, we can start coding the feature. We would love for you to code it. So please open up a WIP (work in progress) pull request, and happy coding.