You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main role of Kamaji Control Plane is just for linking with CAPI. So, we need to check TCP(tenant Control Plane) if we want to check the status of control plane in detail.
That's why this repo's name is cluster-api-control-plane-provider-kamaji, not cluster-api-control-plane-kamaji.
I suggest renaming the CRD's name to KamajiControlPlaneProvider.
$: kubectl get kamajicontrolplaneprovider
NAME VERSION INITIALIZED READY AGE
capi-quickstart 1.23.10 true true 60d
The main role of Kamaji Control Plane is just for linking with CAPI. So, we need to check TCP(tenant Control Plane) if we want to check the status of control plane in detail.
That's why this repo's name is cluster-api-control-plane-provider-kamaji, not cluster-api-control-plane-kamaji.
I suggest renaming the CRD's name to KamajiControlPlaneProvider.
Related to #66
The text was updated successfully, but these errors were encountered: