Troubleshoot MicroK8s

Common issues

  1. After starting microk8s with the microk8s start command, microk8s status outputs that microk8s is not started.

    Ensure there is a default gateway configured for the machine:

    ip route | grep default

    If this is not the case, please add it:

    ip route add default via $(hostname -I | cut -d" " -f1)
  2. The containers are is the Running state but the web interface responds with 502 errors.

    Verify the firewall configuration. In particular, with Red Hat based distributions, the NAT source rule must be enabled:

    firewall-cmd --add-masquerade --permanent
    firewall-cmd --reload
    sudo su - cyberwatch
    cd cbw-on-premise
    ./ restart

Back to top