Angelos Kolaitis

Hi @romainrossi Can you share the output of `mount | grep cgroup` on your machine? Can you also check if the commands below resolve your issue? They should force MicroK8s...

Hi @romainrossi Looking at the attached tarball, the cluster seems to be running fine (see output of kubectl below). Could it be that this is just a false alarm from...

``` FAIL: Service snap.microk8s.daemon-apiserver-proxy is not running ``` This is a false alarm, the apiserver-proxy is only needed for MicroK8s worker nodes. There should be a `no-apiserver-proxy` file under `var/lock/`...

Hi @zhhuabj, this does not sound like a solution that would work in all cases. Can you check if the documentation in https://microk8s.io/docs/registry-private#configure-registry-mirrors-7 helps you resolve the issue? Thanks!

Hi @rogermartensson, Could this be `10` vs `10G`? Can you try with `microk8s install --size=10G`?

Hi @wisaaco This is most likely related to having two default interfaces on your machines. Can you elaborate on the steps that were taken when creating the cluster? (That is,...

Hi @laiqinghua. You need to configure the following arguments for this (assuming the two node interfaces are 192.168.1.5 and 10.10.10.5): In `/var/snap/microk8s/current/args/kube-apiserver`, set the following: ``` --advertise-address=10.10.10.5 ``` Then, in...

Update: We are working on getting MicroK8s to build on ppc64le architectures, and it will be supported (starting with version 1.25 in August 2022)

Hi @tinklern. Thank you for bringing this to our attention, the documentation page has been updated and the change will be reflected shortly.

@debimishra89 Note that the GPU addon is broken in 1.21. MicroK8s 1.21 is also out of support, so we have no immediate plans to change it. However, it is possible...