# MicroK8s v1.20 released!

**URL:** <https://discuss.kubernetes.io/t/microk8s-v1-20-released/14060>\
**Category:** microk8s\
**Created:** [December 11, 2020, 2:43pm UTC](https://discuss.kubernetes.io/t/microk8s-v1-20-released/14060 "2020-12-11T14:43:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kjackal](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/kjackal/32/1750_2.png) [@kjackal](https://discuss.kubernetes.io/u/kjackal)\
**Post date:** [December 11, 2020, 2:43pm UTC](https://discuss.kubernetes.io/t/microk8s-v1-20-released/14060/1 "2020-12-11T14:43:21Z")

</div>

[MicroK8s](https://microk8s.io/) is a Kubernetes cluster delivered as a single snap package - it can be installed on any Linux distribution which supports [snaps](https://snapcraft.io/), as well as macOS and Windows 10. With a quick install, easy upgrades, and great security Microk8s is perfect for micro clouds and edge computing. Try it on your laptop!

```auto

snap install microk8s --classic --channel=1.20/stable

```

Most important updates since the last release:

- Kubeflow updated to v1.1
- Make MicroK8s [failure domain aware](https://discuss.kubernetes.io/t/high-availability-ha/11731)
- Addons can now use `--foo` arguments
- New addon: [KEDA](https://keda.sh/). Thank you [@balchua](https://github.com/balchua)
- New addon: Portainer. Many thanks [@balasu](https://github.com/balasu)
- Try out Traefik v2.3 ingress with `microk8s enable traefik`. Thanks [@balasu](https://github.com/balasu)
- Prometheus monitoring available for ARM64, thank you [@balchua](https://github.com/balchua)
- Linkerd updated to v2.9.0 and available for ARM64, thank you [@balchua](https://github.com/balchua)
- Ingress updated to v0.35.0, thank you [@balchua](https://github.com/balchua)
- Cilum updated to v1.8.3, thank you [@balchua](https://github.com/balchua) and [@joestringer](https://github.com/joestringer)
- Juju updated to 2.8
- Option to set forward DNS servers when enabling DNS. Thank you [@RiyaJohn](https://github.com/RiyaJohn)
- `--help` argument in `microk8s inspect`, thank you [@bowers](https://github.com/bowers)
- fix race condition in setting the registry configmap, thank you [@nicks](https://github.com/nicks)

Make sure you also check out the [support for Kata Containers](https://github.com/didier-durand/microk8s-kata-containers) and the [Akri integration](https://github.com/didier-durand/microk8s-akri) by [@didier-durand](https://github.com/didier-durand).

Users following the latest stable MicroK8s track will be automatically upgraded to 1.20 in the next couple of days.

For more information on MicroK8s consult the official [docs](https://microk8s.io/docs/), and to contribute to the project, check out the repo at [https://github.com/ubuntu/microk8s](https://github.com/ubuntu/microk8s), or chat with us on the [Kubernetes Slack](http://slack.kubernetes.io/), in the #microk8s channel!

---

<div class="post-metadata">

**Author:** ![christopher.parker](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/christopher.parker/32/6488_2.png) [@christopher.parker](https://discuss.kubernetes.io/u/christopher.parker)\
**Post date:** [December 16, 2020, 4:55pm UTC](https://discuss.kubernetes.io/t/microk8s-v1-20-released/14060/2 "2020-12-16T16:55:52Z")

</div>

Is there any way to configure the microk8s Windows installer to use a different drive for creating the VM? It’s defaulting to the C: drive, but I need it to use the D: drive. _(Apologies if this question belongs elsewhere.)_