Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tsuWW opened this issue Oct 25, 2023 · 3 comments

Comments

@tsuWW
Copy link

tsuWW commented Oct 25, 2023

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
Copy link

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

Can you share the cluster template you are using? Thanks

@tsuWW
Copy link
Author

tsuWW commented Oct 25, 2023

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

@tsuWW
Copy link
Author

tsuWW commented Oct 26, 2023

Hello, has anyone been able to look into this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants