Open snehala27 opened 11 months ago
Hi @snehala27, thank you for raising the issue. I don't think any logs are needed, I can see where the issue comes from
Is this issue resolved? @neoaggelos
Hi @roshanirathi, for some context:
The issue is resolved in the 1.28/edge
MicroK8s and will be promoted to 1.28/stable
with the next minor release in a few days. Minor releases are promoted to stable typically after a week of successful CI runs.
$ sudo snap info microk8s | grep 1.28/
1.28/stable: v1.28.3 2023-11-12 (6089) 185MB classic
1.28/candidate: v1.28.3 2023-10-30 (6089) 185MB classic
1.28/beta: v1.28.3 2023-10-30 (6089) 185MB classic
1.28/edge: v1.28.4 2023-11-15 (6225) 185MB classic
To your question, the fix will be released to stable by this week.
On creating a 3CP-1Worker node cluster, the first CP node comes fine and the other 2 CP machines stay in provisioning state. On AWS console, all the three CP machines are created.
Same for 1CP-1Worker node cluster. CP node comes fine and worker node never joins the cluster. On logging into worker node, microk8s status says that the node has joined master
Let me know if any logs are required