OCM Hub Control Plane

KubeVela’s native multi-cluster functionalities is basically working based on the cluster-gateway which is responsible for routing and proxying kube api requests to the “controllee clusters”. The cluster-gateway is an aggregated apiserver that plugs a new “clustergateways/proxy” resource into the hosting cluster where your KubeVela controller is running, and it will help you deliver your requesting payload to the target cluster without reading the client credentials. So the KubeVela controller will be able to dynamically automate the multiple clusters configured/discovered.

(Open Cluster Manager) is a modular, extensible, multi-cluster platform providing various multi-cluster functionalities as atomic “building blocks” to orchestrate their multi-cluster control plane. A minimal setup of OCM merely covers the installation of a registration-operator which is a typical Kubernetes operator that helps install/upgrade OCM components for us.

The overall status of the “OCM Cluster Manager” addon is visible by the following command in which you can clearly see if there’s anything going wrong with the addon installation:

Given that this addon doesn’t actually start the integration between OCM and cluster-gateway, we will need to either manually sync the cluster metadata from vela to OCM or go on enable the “ocm-gateway-manager-addon” addon to let the addon-manager do the automatic synchronization.

Then the joining cluster is supposed to be listed as a in terms of your OCM control plane:

After your OCM environment is all set, you can delegate the cluster registration to OCM by installation additional OCM modules including:

An illustrative instruction for registering clusters via OCM is already prepared for you over here:

Please reach out to the KubeVela official dev squad for the support.

Last updated on Feb 9, 2023 by dependabot[bot]