Syncing Kubernetes Clusters for CD
Create or link your clusters to Ozone for the purpose of CI/CD automation and workload observability
Syncing clusters to Ozone for workload deployments
With ozone, sync clusters using our interface and map it to deployment environments. To sync a cluster, you must have a cloud provider integration added from the Setup section.
Once you've got the credentials setup in the form of a cloud provider, you can now use ozone to deploy container workloads, run CI/CD workflows and gain improved observability for container workloads.
Any cluster that is synced is scoped to the current project. To use this cluster in another project, an account admin must add it to another project.
Integrate a cloud provider with Ozone (Supported providers are AWS, GCP and Azure)
Once a cloud provider is created, clusters are automatically synced back to ozone
You can also sync any clusters added to your account post the first sync by clicking on the "Sync Cluster" button
Flow Summary:
Attaching an existing cluster to Ozone
Any cluster that is attached is scoped to the current project. To use this cluster in another project, an account admin must add it to another project.
Use this option if the cluster is located on-premise from distributions such as PKS, TKG and Openshift.
This is the typical use case, but in theory you can attach any CNCF compliant Kubernetes cluster (including public clouds)
Navigate to Resources -> Clusters
Click on +ATTACH
Enter the cluster name
Select the type of the cluster (Distribution type)
If the cluster has no exposed API service, do mark it as a private cluster
In this case, ozone sets up a private software defined network to enable you to perform automated CI/CD for container workloads.
Apply the YAML file on the cluster by using the commands shown on the screen
The cluster should now be synced to the Resources -> Cluster section
Once the cluster is linked successfully, it will be visible with an Active Status and a Green Check mark for Ozone's Agent status, indicating that it has successfully been created and setup.
Getting your clusters ready for CI/CD
Enable the following settings from either:
The CI/CD Settings screen as the last step before the cluster is created
Edit screen of the cluster once it has been synced to ozone (Resources -> Cluster -> Select Cluster -> Edit)
Supported CI/CD Settings for automation and observability:
| Setting | Function |
|---|---|
Enable Metrics Monitoring | Installs components necessary for unified workload metrics observability |
Enable Logging | Enables workload logs specific to those of Ozone components installed on this cluster |
Enable Logging on All Namespaces | Enables workload logs across all namespaces on this cluster. |
Enable Helm Charts | Installs components necessary for handling helm chart deployments on this cluster |
Enable Operators | Installs components necessary to deploy operators on this cluster |
Enable Tekton Pipelines | Installs Tekton components which enables you to deploy microservices to any cluster |
Enable Automated Canary | Installs components required to perform an automated canary analysis on this cluster |
Enable Istio | Installs components from istio for routing metric traffic for canary analysis |
Enable Backups | Installs components which are capable of handling namespace level snapshots for on-demand restoration to any K8s Cluster |
Last updated