Kubernetes-native declarative infrastructure for OCI.
The Cluster API Provider for OCI (CAPOCI) brings declarative, Kubernetes-style APIs to cluster creation, configuration and management.
The Cluster API itself is shared across multiple cloud providers allowing for true hybrid deployments of Kubernetes.
- Self-managed and OCI Container Engine for Kubernetes(OKE) clusters
- Manages the bootstrapping of VCNs, gateways, subnets, network security groups
- Provide secure and sensible defaults
You can find detailed documentation as well as a getting started guide in the Cluster API Provider for OCI Book.
The CAPOCI provider is developed in the open, and is constantly being improved by our users, contributors, and maintainers.
To ask questions or get the latest project news, please join us in the [#cluster-api-oci][#cluster-api-oci] channel on Slack.
The maintainers host office hours on the first Tuesday of every month at 06:00 PT / 09:00 ET / 14:00 CET / 18:00 IST via Zooom.
All interested community members are invited to join us. A recording of each session will be made available afterwards for folks who are unable to attend.
Previous meetings: [ notes | recordings (coming soon) ]
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.
CAPOCI supports the following Cluster API versions.
Cluster API v1beta1 (v1.x.x) |
|
|---|---|
OCI Provider (v0.x.x) |
✓ |
CAPOCI provider is able to install and manage the versions of Kubernetes supported by Cluster API (CAPI).
This project welcomes contributions from the community. Before submitting a pull request, please review our contribution guide
Please consult the security guide for our responsible security vulnerability disclosure process
Copyright (c) [2021, 2022] year Oracle and/or its affiliates.
Released under the Apache License License Version 2.0 as shown at http://www.apache.org/licenses/.