Release channels and upgrades
Microk8s is a snap deploying Kubernetes. Upstream Kubernetes ships a new release about
every three months, while old releases get periodic updates. Currently, the latest release
v1.14.1 being the latest release. On the
is the latest release. It is important to remember that upstream Kubernetes is committed
to maintain backwards compatibility only within a release series. That means that
your Kubernetes will not break when you upgrade from
v1.14.y but may
break if you upgrade from
Choosing the right channel
When installing MicroK8s you can select your desired upstream Kubernetes series with the
corresponding snap channel. All channels are shown with
snap info microk8s:
channels: stable: v1.14.1 2019-04-18 (522) 214MB classic candidate: v1.14.1 2019-04-15 (522) 214MB classic beta: v1.14.1 2019-04-15 (522) 214MB classic edge: v1.14.1 2019-05-10 (587) 217MB classic 1.15/stable: – 1.15/candidate: – 1.15/beta: – 1.15/edge: v1.15.0-alpha.3 2019-05-08 (578) 215MB classic 1.14/stable: v1.14.1 2019-04-18 (521) 214MB classic 1.14/candidate: v1.14.1 2019-04-15 (521) 214MB classic 1.14/beta: v1.14.1 2019-04-15 (521) 214MB classic 1.14/edge: v1.14.1 2019-05-11 (590) 217MB classic 1.13/stable: v1.13.5 2019-04-22 (526) 237MB classic 1.13/candidate: v1.13.6 2019-05-09 (581) 237MB classic 1.13/beta: v1.13.6 2019-05-09 (581) 237MB classic 1.13/edge: v1.13.6 2019-05-08 (581) 237MB classic 1.12/stable: v1.12.8 2019-05-02 (547) 259MB classic 1.12/candidate: v1.12.8 2019-05-01 (547) 259MB classic 1.12/beta: v1.12.8 2019-05-01 (547) 259MB classic 1.12/edge: v1.12.8 2019-04-24 (547) 259MB classic 1.11/stable: v1.11.10 2019-05-10 (557) 258MB classic 1.11/candidate: v1.11.10 2019-05-02 (557) 258MB classic 1.11/beta: v1.11.10 2019-05-02 (557) 258MB classic 1.11/edge: v1.11.10 2019-05-01 (557) 258MB classic 1.10/stable: v1.10.13 2019-04-22 (546) 222MB classic 1.10/candidate: v1.10.13 2019-04-22 (546) 222MB classic 1.10/beta: v1.10.13 2019-04-22 (546) 222MB classic 1.10/edge: v1.10.13 2019-04-22 (546) 222MB classic
To install MicroK8s and let it follow the
v1.14 release series you:
snap install microk8s --classic --channel=1.14/stable
If you omit the
--channel argument MicroK8s will follow the latest stable upstream
Kubernetes. This means that your deployment will eventually upgrade to a new release
series. For example, at the time of writing you will get
snap install microk8s --classic
--channel is specified, such a deployment will eventually upgrade to
Tracks with stable releases
*/stable channels serve the latest stable upstream Kubernetes release of the
respective release series. Upstream releases are propagated to the MicroK8s snap in about
a week. This means your MicroK8s will upgrade to the latest upstream release in your
selected channel roughly one week after the upstream release.
*/beta channels get updated within hours of an upstream release.
Getting a MicroK8s deployment pointing to
1.14/beta is as simple as:
snap install microk8s --classic --channel=1.14/beta
*/edge channels get updated on each MicroK8s patch or upstream Kubernetes patch release.
Keep in mind that edge and beta are snap constructs and do not relate to specific Kubernetes release names.
Tracks with pre-stable releases
On tracks where no stable Kubernetes release is available, MicroK8s ships pre-release versions under the following scheme:
1.15/edge) holds the alpha upstream releases.
1.15/beta) holds the beta upstream releases.
1.15/candidate) holds the release candidate of upstream releases.
Pre-release versions will be available the same day they are released upstream.
For example, assuming
v1.14 is the latest stable release, to test your work against the
v1.15 release simply run:
sudo snap install microk8s --classic --channel=1.5/edge
However, be aware that pre-release versions may require you to configure the K8s services on your own.
I am confused. Which channel is right for me?
The single question you need to focus on is what channel should be used below:
sudo snap install microk8s --classic --channel=<which_channel?>
Here are some suggestions for the channel to use based on your needs:
I want to always be on the latest stable Kubernetes.
I want to always be on the latest release in a specific upstream K8s release.
I want to test-drive a pre-stable release.
--channel=<next_release>/edgefor alpha releases.
--channel=<next_release>/betafor beta releases.
--channel=<next_release>/candidatefor candidate releases.
I am waiting for a bug fix on MicroK8s:
I am waiting for a bug fix on upstream Kubernetes: