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
I noticed several issues with the ManagedCluster CR:
Name ManagedCluster clashes with the resource ManagedCluster of containerservice.azure.com/v1api20210501 which is a part of Azure provider. This means that user can't execute kubectl get managedcluster and has to user the full name kubectl get managedcluster.v1alpha1.hmc.mirantis.com
Short names of the ManagedCluster are hmc-deploy and deploy which make confusion even more.
The task
Replace short names to be similar to the full name. In the docs if ManagedCluster resource is mentioned in scope of kubectl commands it should referenced by a full name with group and version (managedcluster.v1alpha1.hmc.mirantis.com).
The text was updated successfully, but these errors were encountered:
I noticed several issues with the
ManagedCluster
CR:ManagedCluster
clashes with the resourceManagedCluster
ofcontainerservice.azure.com/v1api20210501
which is a part of Azure provider. This means that user can't executekubectl get managedcluster
and has to user the full namekubectl get managedcluster.v1alpha1.hmc.mirantis.com
ManagedCluster
arehmc-deploy
anddeploy
which make confusion even more.The task
Replace short names to be similar to the full name. In the docs if
ManagedCluster
resource is mentioned in scope of kubectl commands it should referenced by a full name with group and version (managedcluster.v1alpha1.hmc.mirantis.com
).The text was updated successfully, but these errors were encountered: