search

canonical / cluster-api-bootstrap-provider-microk8s

This project offers a cluster API bootstrap provider controller that manages the node provision of a MicroK8s cluster.
https://microk8s.io
21 stars 14 forks source link

Cluster Secrets <cluster-name>-ca and <cluster-name>-jointoken not generating #83

Open tsuWW opened 10 months ago

tsuWW commented 10 months ago

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

neoaggelos commented 10 months ago

Hi @tsuWW , we do not have a cluster template for vsphere (yet).

Can you share the cluster template you are using? Thanks

tsuWW commented 10 months ago

Hi @neoaggelos, here is the cluster-template I created. Not sure if its 100% correct. microk8s-vsphere-clusterctl.txt

tsuWW commented 10 months ago

Hello, has anyone been able to look into this?