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
Using the Microk8s Bootstrap and Microk8s Control Plane with the vSphere Infrastructure Provider, the secrets for the ca and jointoken are not generating. Is this expected behavior? The only logs I see are that the <cluster-name>-ca secret is missing but nothing about why it didn't generate. I did not see this behavior when using AWS as the infrastructure provider.
When I do a kubectl describe cluster <cluster-name> , I see a status of Waiting for control plane provider to indicate the control plane has been initialized.
Using a Multipass vm on Ubuntu 22.04
kubectl client version: v1.28.3
kubectl server version: v1.27.6
clusterctl version: v1.5.3
microk8s version: v1.27.6 revision 6070
The text was updated successfully, but these errors were encountered:
Using the Microk8s Bootstrap and Microk8s Control Plane with the vSphere Infrastructure Provider, the secrets for the ca and jointoken are not generating. Is this expected behavior? The only logs I see are that the
<cluster-name>-ca
secret is missing but nothing about why it didn't generate. I did not see this behavior when using AWS as the infrastructure provider.When I do a
kubectl describe cluster <cluster-name>
, I see a status ofWaiting for control plane provider to indicate the control plane has been initialized.
Using a Multipass vm on Ubuntu 22.04
kubectl client version: v1.28.3
kubectl server version: v1.27.6
clusterctl version: v1.5.3
microk8s version: v1.27.6 revision 6070
The text was updated successfully, but these errors were encountered: