Kubernetes-native declarative infrastructure for GCP.
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 Google Cloud hybrid deployments of Kubernetes.
Checkout our Cluster API Quick Start to create your first Kubernetes cluster on Google Cloud Platform using Cluster API.
This provider's versions are compatible with the following versions of Cluster API:
Cluster API v1alpha2 (v0.2.x) |
Cluster API v1alpha3 (v0.3.x) |
Cluster API v1alpha4 (v0.4.x) |
|
|---|---|---|---|
Google Cloud Provider v0.2.x |
✓ | ||
Google Cloud Provider v0.3.x |
✓ | ||
Google Cloud Provider v0.4.x |
✓ |
This provider's versions are able to install and manage the following versions of Kubernetes:
Google Cloud Provider v0.2.x |
Google Cloud Provider v0.3.x |
Google Cloud Provider v0.4.x |
|
|---|---|---|---|
| Kubernetes 1.15 | ✓ | ||
| Kubernetes 1.16 | ✓ | ✓ | |
| Kubernetes 1.17 | ✓ | ||
| Kubernetes 1.18 | ✓ | ✓ | |
| Kubernetes 1.19 | ✓ | ✓ | |
| Kubernetes 1.20 | ✓ | ✓ | |
| Kubernetes 1.21 | ✓ | ✓ | |
| Kubernetes 1.22 | ✓ |
Each version of Cluster API for Google Cloud will attempt to support atleast two version of Kubernetes versions e.g., Cluster API for GCP v0.1 may support Kubernetes 1.13 and Kubernetes 1.14.
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.
Presently our docs can be found here.
Are you interested in contributing to cluster-api-provider-gcp? We, the maintainers and the community, would love your suggestions, support and contributions! The maintainers of the project can be contacted anytime to learn about how to get involved.
Before starting with the contribution, please go through prerequisites of the project.
To set up the development environement checkout the development guide.
In the interest of getting new people involved we have issues marked as good first issue. Although
this issues have a smaller scope but are very helpful in getting acquainted with the codebase.
For more see the issue tracker. If you're unsure where to start, feel free to reach out to discuss.
See also: Our own contributor guide and the Kubernetes community page.
We also encourage ALL active community participants to act as if they are maintainers, even if you don't have 'official' written permissions. This is a community effort and we are here to serve the Kubernetes community. If you have an active interest and you want to get involved, you have real power!
- Join the SIG Cluster Lifecycle Google Group for access to documents and calendars.
- Participate in the conversations on Kubernetes Discuss
- Provider implementers office hours (CAPI)
- Weekly on Wednesdays @ 10:00 PT on Zoom
- Previous meetings: [ notes | recordings ]
Please check in with us in the #cluster-api-gcp on Slack.
If you think you have found a bug please follow the instruction below.
- Please give a small amount of time giving due diligence to the issue tracker. Your issue might be a duplicate.
- Get the logs from the custom controllers and please paste them in the issue.
- Open a bug report.
- Remember users might be searching the issue in future, so please make sure to give it a meaningful title to help others.
- Feel free to reach out to the community on slack.
We also have a issue tracker to track features. If you think you have a feature idea, that could make Cluster API provider GCP become even more awesome, then follow these steps.
- Open a feature request.
- Remember users might be searching for the issue in future, so please make sure to give it a meaningful title to help others.
- Clearly define the use case with concrete examples. Example: type
thisand cluster-api-provider-gcp doesthat. - Some of our larger features will require some design. If you would like to include a techincal design to your feature, please go ahead.
- After the new feature is well understood, and the design is 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) PR and happy coding!
Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.