MicroK8s Documentation

MicroK8s is the smallest, fastest, fully-conformant Kubernetes that tracks upstream releases and makes clustering trivial. MicroK8s is great for offline development, prototyping, and testing. Use it on a VM as a small, cheap, reliable k8s for CI/CD. It’s also the best production grade Kubernetes for appliances. Develop IoT apps for k8s and deploy them to MicroK8s on your Linux boxes.

What you’ll need

  • An Ubuntu 20.04 LTS, 18.04 LTS or 16.04 LTS environment to run the commands (or another operating system which supports snapd - see the snapd documentation)
  • At least 20G of disk space and 4G of memory are recommended
  • An internet connection

Note: If you don’t meet these requirements, there are additional ways of installing MicroK8s, including additional OS support and an offline deploy. See the alternative install page for details.

  1. Install MicroK8s

    MicroK8s will install a minimal, lightweight Kubernetes you can run and use on practically any machine. It can be installed with a snap:

    sudo snap install microk8s --classic --channel=1.21

    More about setting the channel

  2. Join the group

    MicroK8s creates a group to enable seamless usage of commands which require admin privilege. To add your current user to the group and gain access to the .kube caching directory, run the following two commands:

    sudo usermod -a -G microk8s $USER
    sudo chown -f -R $USER ~/.kube

    You will also need to re-enter the session for the group update to take place:

    su - $USER

  3. Check the status

    MicroK8s has a built-in command to display its status. During installation you can use the --wait-ready flag to wait for the Kubernetes services to initialise:

    microk8s status --wait-ready

  4. Access Kubernetes

    MicroK8s bundles its own version of kubectl for accessing Kubernetes. Use it to run commands to monitor and control your Kubernetes. For example, to view your node:

    microk8s kubectl get nodes

    …or to see the running services:

    microk8s kubectl get services

    MicroK8s uses a namespaced kubectl command to prevent conflicts with any existing installs of kubectl. If you don’t have an existing install, it is easier to add an alias (append to ~/.bash_aliases) like this:

    alias kubectl='microk8s kubectl'

  5. Deploy an app

    Of course, Kubernetes is meant for deploying apps and services. You can use the kubectl command to do that as with any Kuberenetes. Try installing a demo app:

    microk8s kubectl create deployment nginx --image=nginx

    It may take a minute or two to install, but you can check the status:

    microk8s kubectl get pods

  6. Use add-ons

    MicroK8s uses the minimum of components for a pure, lightweight Kubernetes. However, plenty of extra features are available with a few keystrokes using “add-ons” - pre-packaged components that will provide extra capabilities for your Kubernetes, from simple DNS management to machine learning with Kubeflow!

    To start it is recommended to add DNS management to facilitate communication between services. For applications which need storage, the ‘storage’ add-on provides directory space on the host. These are easy to set up:

    microk8s enable dns storage

    See the full list of addons

  7. Starting and Stopping MicroK8s

    MicroK8s will continue running until you decide to stop it. You can stop and start MicroK8s with these simple commands:

    microk8s stop

    … will stop MicroK8s and its services. You can start again any time by running:

    microk8s start

    Note that if you leave MicroK8s running, it will automatically restart after a reboot. If you don’t want this to happen, simply remember to run microk8s stop before you power down.

Next steps


Level Path Navlink
0 Install
1 / Getting started
1 install-alternatives Alternative install methods
2 install-alternatives#heading–windows Windows10
2 install-alternatives#heading–macos macOS
2 install-alternatives#heading–arm Raspberry PI/ARM
2 install-alternatives#heading–offline Offline installs
1 lxd LXD
1 install-proxy Behind a proxy
1 setting-snap-channel Channels and versions
1 upgrading Upgrading
0 Add-ons
1 addons Enabling and disabling
2 addons#heading–list Available add-ons
0 Additional configuration
1 high-availability High Availability
1 configuring-services Configuring services
1 clustering Multi-node cluster
1 ports#heading–auth Authentication and authorization
1 external-lma Adding an LMA stack
1 multi-user Multi-user setup
1 change-cidr Changing the pod CIDR
1 add-a-windows-worker-node-to-microk8s Adding Windows workers
0 Images and registries
1 registry-images Using local images
1 registry-public Using a public registry
1 registry-built-in Using the built-in registry
1 registry-private Using a private registry
0 Troubleshooting
1 troubleshooting How to diagnose problems
1 troubleshooting#heading–inspect Using microk8s.inspect
1 troubleshooting#heading–common-issues Common issues
1 troubleshooting#heading–report-bug Reporting a bug
0 Reference
1 release-notes Release notes
1 command-reference Command reference
1 services-and-ports Services and ports used
1 working-with-kubectl Working with kubectl
1 get-in-touch Get in touch
1 docs/docs Contributing to docs


Mapping table
Path Location