A control plane of type "ocm" can be created using a vcluster control plane and then deploying OCM there. This would allow to use the stock OCM images and deployment methods, instead than the current approach based on multicluster-controlplane. From initial testing, this works well but for the dev scenario with kind clusters we need to support the internal address used by kind clusters on the same docker network so that managed clusters can contact the hub using the internal address and nodeport, as currently happens with the [basic OCM scenario](https://open-cluster-management.io/getting-started/quick-start/
Proposed Solution
To support the communication between OCM hub on kind and managed kind clusters on the same docker network, we need to do the following:
[x] Add kubeflex-control-plane to the SANs for the vcluster API server TLS certs
[x] Add a NodePort service for vcluster (or change the current vcluster service from ServiceIP to NodePort)
[x] Get the value assigned to the NodePort
[x] Update the cluster-info config map in the kube-public namespace so that it points to the address https://kubeflex-control-plane:<NodePort>
Feature Description
A control plane of type "ocm" can be created using a vcluster control plane and then deploying OCM there. This would allow to use the stock OCM images and deployment methods, instead than the current approach based on multicluster-controlplane. From initial testing, this works well but for the dev scenario with kind clusters we need to support the internal address used by kind clusters on the same docker network so that managed clusters can contact the hub using the internal address and nodeport, as currently happens with the [basic OCM scenario](https://open-cluster-management.io/getting-started/quick-start/
Proposed Solution
To support the communication between OCM hub on kind and managed kind clusters on the same docker network, we need to do the following:
kubeflex-control-planeto the SANs for the vcluster API server TLS certscluster-infoconfig map in thekube-publicnamespace so that it points to the addresshttps://kubeflex-control-plane:<NodePort>Want to contribute?
Additional Context
No response