Oracle Cloud Native Environment is a fully integrated suite for the development and management of cloud-native applications. Oracle Cloud Native Environment is a curated set of open source projects that are based on open standards, specifications and APIs defined by the Open Container Initiative (OCI) and Cloud Native Computing Foundation (CNCF) that can be easily deployed, have been tested for interoperability and for which enterprise-grade support is offered. Oracle Cloud Native Environment delivers a simplified framework for installations, updates, upgrades and configuration of key features for orchestrating microservices.
Cluster API can be extended to support any infrastructure (AWS, Azure, vSphere, etc.), bootstrap or control plane provider (kubeadm is built in). There is a growing list of supported providers available.
OCNE Provider for CAPI (CAPOCNE) is used to bootstrap and control OCNE instances on top of major infrastructure providers like OCI, AWS and Azure. This extends the kubeadm bootstrap and control plane provider functionality. The OCNE Provider does not use pre-baked images but rather uses vanilla OL8 images and installs the dependancies at boot time.
CAPOCNE supports the following Cluster API versions.
Cluster API v1beta1 (v1.x.x) |
|
|---|---|
OCNE Provider (v0.x.x) |
✓ |
CAPOCNE enables dynamic installation of dependencies without the need to maintain images per region. The following is the support matrix for CAPOCNE:
| Operating System | Infrastructure Provider |
|---|---|
| Oracle Linux 8 | CAPOCI |
CAPOCNE provider follows the below support matrix with regards Kubernetes distribution. All images are hosted at container-registry.oracle.com.
| K8s Version | DNS Image Tag | ETCD Image Tag |
|---|---|---|
| 1.25.7 | v1.9.3 | 3.5.6 |
| 1.25.11 | v1.9.3 | 3.5.6 |
| 1.26.6 | v1.9.3 | 3.5.6 |
- Install clusterctl following the upstream instructions
curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.4.3/clusterctl-linux-amd64 -o clusterctl
- Install a Kubernetes cluster using KinD:
cat > kind-cluster-with-extramounts.yaml <<EOF
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
extraMounts:
- hostPath: /var/run/docker.sock
containerPath: /var/run/docker.sock
EOF
kind create cluster --config kind-cluster-with-extramounts.yaml
- To install the OCNE providers, convert the existing KIND cluster created above into a management cluster. Update the
clusterctlconfiguration file~/.cluster-api/clusterctl.yamlto point to the release artifacts folder:
providers:
- name: "ocne"
url: "https://github.com/verrazzano/cluster-api-provider-ocne/releases/v1.7.0/bootstrap-components.yaml"
type: "BootstrapProvider"
- name: "ocne"
url: "https://github.com/verrazzano/cluster-api-provider-ocne/releases/v1.7.0/control-plane-components.yaml"
type: "ControlPlaneProvider"You will now be able to initialize clusterctl with the OCNE providers:
clusterctl init --bootstrap ocne:v1.7.0 --control-plane ocne:v1.7.0 -i oci:v0.12.0
NOTE: Currently OCNE Provider is verified only for the OCI infrastructure provider. Follow the instructions here for setting up OCI provider.
- Once initialization is complete pods such as the following should be running in the cluster
capi-ocne-bootstrap-system capi-ocne-bootstrap-controller-manager-7cd89b4bbb-bwsbs 1/1 Running 0 34m
capi-ocne-control-plane-system capi-ocne-control-plane-controller-manager-5cdf88667f-vqq27 1/1 Running 0 34m
capi-system capi-controller-manager-8b477f66b-tcgcg 1/1 Running 0 34m
cluster-api-provider-oci-system capoci-controller-manager-5f5d9d49b5-mht2p 1/1 Running 0 34mWhen the OCNE bootstrap and control plane clusters are up and running you can apply cluster manifests with the desired specs to provision a cluster of your choice.
OCNE provider configuration is similar to Kubeadm configuration with some additional properties. For example, the proxy property may be required to enable dependency installation in environmentis that have a proxy configured. For such a case, the spec.controlPlaneConfig.proxy property can be set in the OCNEControlPlane object and spec.proxy.httpProxy in the OCNEConfigTemplate.
You may also find useful manifests for property configuration under the examples directory.
- Generate and deploy the cluster
source examples/variables.env
clusterctl generate cluster ocne-cluster --from-file examples/module-operator/cluster-template-existingvcnwithaddons.yaml | kubectl apply -f -- Once the cluster is deployed successfully you should see a cluster description similar to the following:
clusterctl describe cluster ocne-cluster
NAME READY SEVERITY REASON SINCE MESSAGE
Cluster/ocne-cluster True 45m
ClusterInfrastructure - OCICluster/ocne-cluster True 56m
ControlPlane - OCNEControlPlane/ocne-cluster-control-plane True 45m
Machine/ocne-cluster-control-plane-z47bj True 55m
Workers
MachineDeployment/ocne-cluster-md-0 True 36m
Machine/ocne-cluster-md-0-846df89cb4-dbrdn True 44mIf your project has specific contribution requirements, update the CONTRIBUTING.md file to ensure those requirements are clearly explained
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
The correct copyright notice format for both documentation and software is "Copyright (c) [year,] year Oracle and/or its affiliates." You must include the year the content was first released (on any platform) and the most recent year in which it was revised
Copyright (c) 2023 Oracle and/or its affiliates.
Replace this statement if your project is not licensed under the UPL
Released under the Universal Permissive License v1.0 as shown at https://oss.oracle.com/licenses/upl/.