Berkay Tekin Öz

Hi @relief-melone Thanks for reaching out. This indeed seems like a proxy related issue, I am suspecting there might be some missing configuration. Could you share your `HTTPS_PROXY`, `HTTP_PROXY` and...

Hi @sign-out Thanks for reaching out. Sorry to hear that you have trouble joining nodes. Could you please run `microk8s inspect` and attach the generated tarball for the nodes you...

Hi @tmpm697 Thanks for reaching out. `microk8s reset` command is the correct way to have a clean reset. The command first clears and stops everything including the CNI, and then...

Hey @niksacdev, Sorry to hear that you are having trouble with your installation. Could you please attach the tarball generated by the `microk8s inspect` command? Thanks.

Hey @naphtalidavies, thank you for reaching out. We have not come across a similar scenario, were there any operations such as a snap refresh or some addon being enabled at...

Hey @VitorNilson, Seems like there are some missing setup steps. I'd suggest checking out our [MetalLB docs](https://microk8s.io/docs/addon-metallb), which explains how the setup should work. Thanks.

> Why is a join token being generated for a system that does not yet exist? Is it possible to change this flow so that the system is created first,...

Hey @managerkoffi, This seems like #4361. We've backported a workaround to 1.28 this week, in the meantime you can do https://github.com/canonical/microk8s/issues/4361#issuecomment-2336768715 to apply the workaround manually.

Hey @lukasbehammer, Thank you for reporting this. We have a PR https://github.com/canonical/microk8s-core-addons/pull/305 that addresses this on our list. We'll review it and backport to older versions if possible. I'll update...

Hey @AlexGustafsson, Thank you for reporting this issue. Sadly I could not reproduce the issue locally. My initial impression is that this is an upstream regression. We'll try to look...