You should see output similar to the following: Inspecting services To run the inspection tool, enter the command (admin privilege is required to collect all the data): sudo microk8s inspect

This is essential for bug reports, but is also a useful way of confirming the system is (or isn’t) working and collecting all the relevant data in one place. MicroK8s ships with a script to compile a complete report on MicroK8s and the system which it is running on. For more information on the snap environment, check the snap documentation.

Note that the $SNAP_DATA environment variable itself is only available to the running snap. These are available in the directory $/args, which on Ubuntu should point to /var/snap/microk8s/current. If the problem you are experiencing indicates a problem with the configuration of the Kubernetes components themselves, it could be helpful to examine the arguments used to run these components. For example, for the simple redis pod above: microk8s kubectl logs mk8s-redis-7647889b6d-vjwqm You can then use kubectl to view the log. This will list the currently available pods, for example: NAME READY STATUS RESTARTS AGE If a pod is not behaving as expected, the first port of call should be the logs.įirst determine the resource identifier for the pod: microk8s kubectl get pods Be sure to check out the common issues section for help resolving the most frequently encountered problems. But MicroK8s gives you tools to help work out what has gone wrong, as detailed below. It is important to recognise that things can go wrong. Manage upgrades with a Snap Store Proxy.

Daemon tools access denied windows 10