MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
Read more at https://kubernetes.io/blog/2024/04/17/kubernetes-v1-30-release/
With the help of @miro-balaz we identified and patched a few issued that improve the reliability of our default datastore in resource limiting environments.
Most notably
A lot of effort has gone into the datastore, DQlite. In this release we introduced the following improvements:
microk8s version: 1.28 kubectl version: 1.28.3 multipass version: 1.12.2 installer version: 2.3.4
In the past, community members provided instructions on how to configure dual-stack in MicroK8s clusters. From this release onwards, dual-stack along with the respective CIDR configuration can be easily setup with launch configurations even at install time.
You can read more on dual stack over at:
Full CIS compliance can be achieved with a single call: microk8s enable cis-hardening. For auditors and those interested in what each CIS recommendation is about we have assembled a detailed list of each recommendation and how we comply with it. Some of the CIS hardening suggestions have been adopted as default setup options in MicroK8s, for example the authentication of users is now done via x509 certificates instead of tokens.
For the work on this feature you can read:
Try this microk8s enable rook-ceph to get the Rook Ceph operator on your cluster. We found that pairing MicroCeph, the low ops Ceph distribution, with MicroK8s produces a great setup in terms of feature richenss, stability and effectiveness. In our docs we have a guide showing how to testdirve this combination on a single node cluster.
Read more at:
Two addons joined our ecosystems:
KubeArmor is a cloud-native runtime security enforcement system that restricts the behavior (such as process execution, file access, and networking operations) of pods, containers, and nodes at the system level.
MICROCKS is a CNCF project designed to simplify and streamline API mocking and testing, with support for many different types of API and integrations for GitHub, Gitlab, Jenkins and more.
microk8s status will return an error code in case the cluster is not yet ready.microk8s join no longer fails if nodes cannot resolve each other’s hostnames. This limitation has been lifted by updating the default arguments of kube-apiserver.Users can now provide a yaml manifest describing how MicroK8s should be setup. Manifests may specify things like:
MicroK8s consumes configuration manifests found in /root/snap/microk8s/common/ or passed as snap configuration argument via snap set microk8s config=”$(cat microk8s-config.yaml)” as well as through a content interface.
Optimizations in the queries that hit the datastore. This yields a sizable benefit in both latency and CPU utilization. Work on this area is still on-going so expect more improvements in the near future.
The following addons are new in the 1.27 release under the community repo:
microk8s ctr now needs elevated permissions, thank you @balchua
microk8s enable shifu, thank you @saiyan86, @tomqin93
microk8s enable easyhaproxy, thank you @byjg
microk8s enable parking, thank you @byjg
The evolution of the addon ecosystem continues to strengthen MicroK8s. The following addons are new in the 1.26 release under the community repo:
Core addons are Kubernetes services shipped with MicroK8s and supported by Canonical Kubernetes. MicroK8s 1.26 extends the core addon ecosystem with the introduction of MinIO: high-performance, S3 compatible object storage.
Most important updates since the last release:
Kubernetes core services
Usability Improvements
Addon updates
microk8s osm, thank you @naqvis
microk8s enable gopaddle-lite. Thank you @renugadevi-2613.microk8s enable minio
microk8s enable ondat. Thank you @hubvu
microk8s enable kwasm. Thank you @0xE282B0.microk8s enable sosivio. Courtesy of @DanArlowski and the sosivio team.Users following the latest stable MicroK8s track will be automatically upgraded to v1.26 in the next few days. Those who want to upgrade their existing clusters can follow the instructions in our docs. Remember, to call sudo microk8s addons repo update <repo_name> on the addon repositories you would like to fetch updates for.
For more information on MicroK8s consult the official docs or chat with us on the Kubernetes Slack, in the #microk8s channel!
MicroK8s is delivered through Snaps and enjoys the benefits of updates and security features. Now we’re stepping even further in direction by implementing strict confinement as a new availability channel. We’re delighted to now offer our users a confined Kubernetes experience that has restricted host system access and a more restrictive security posture. Try it out with:
snap install microk8s --channel=1.25-strict/stable
We’re constantly striving to improve our user experience and as part of this we want to give you MicroK8s in the fastest way possible. As part of this we’ve reduced our snap size by up to 25% to help you get your Kubernetes up and running faster than ever.
With the introduction of core & community addon repositories, there are new observability, networking and security addons that are generally available in this release.
In order to facilitate offline deployments, faster start up times and local development; we have introduced image sideloading support into MicroK8s 1.25.
You asked for it and we listened. For our community that uses Power9 based machines for acceleration, security and data-intensive workloads; MicroK8s can now be operated on these systems.
Most important updates since the last release:
Kubernetes core services
Usability Improvements
microk8s images import and microk8s images export-local commands, allowing side-loading of OCI images across the whole cluster.microk8s version commandAddon updates
microk8s enable kube-ovn
microk8s enable nfs, thank you @jkosik
microk8s enable osm-edge, thank you @naqvis
Users following the latest stable MicroK8s track will be automatically upgraded to v1.25 in the next few days. Those who want to upgrade their existing clusters can follow the instructions in our docs. Remember, to call sudo microk8s addons repo update <repo_name> on the addon repositories you would like to fetch updates for.
For more information on MicroK8s consult the official docs, and to contribute to the project, check out the repo at https://github.com/ubuntu/microk8s, or chat with us on the Kubernetes Slack, in the #microk8s channel!