Starting with K3s v1.40 (expected to be released in July 2027), the system images that K3s deploys will be pulled from the GitHub Container Registry (ghcr.io/k3s-io) instead of Docker Hub. If you run K3s with the default settings and your nodes have access to the GitHub Container Registry, you don't need to change anything. If you use registry mirrors, private registry, the --system-default-registry flag, or air-gap tarballs, you will need to modify your configuration.

We're announcing this now so you have a few releases to get ready.

Kubernetes v1.37 has officially arrived! This quarter, the K3s developer community and maintainers have focused heavily on making edge Kubernetes deployments even more seamless, reliable, and secure. We are thrilled to share some major milestones, from direct support for modern gateway standards to substantial under-the-hood optimization. 🥳

Kubernetes 1.36 has officially landed! Following our continuous commitment to providing a lightweight yet production-grade Kubernetes distribution, the K3s team and community have put together another incredible milestone release. Here is what's new in the world of K3s.

The cloud-native community is heading to Amsterdam for KubeCon + CloudNativeCon Europe 2026, and Project K3s is excited to be part of the action! As one of the most widely adopted lightweight Kubernetes distributions, K3s continues to empower edge, IoT, and resource-constrained environments across industries.

From satellites to smart farming, K3s is proving that Kubernetes can run anywhere — and this year’s KubeCon is packed with sessions that highlight exactly that.

Kubernetes 1.35 has arrived! As we roll out this latest version, it’s the perfect time to reflect on the significant strides the K3s project has made over the last quarter. 🥳

Slow image pulls can be annoying and may increase Kubernetes startup times over a healthy threshold, particularly in resource-constrained or air-gapped environments. The situation is exacerbated by new AI-driven apps, which often rely on astronomically large images, frequently tens or hundreds of gigabytes. This post dives into mechanisms that K3s makes available to improve the user's experience when handling large images.

The K3s binary bundles all the components needed to run a production-ready, CNCF-conformant Kubernetes cluster including containerd, runc, kubelet, and more. In this post we will discuss how containerd communicates with OCI runtimes and will discuss adding another container runtime (Sysbox) to K3s and how it can be used to run system pods in your environment.

Kubernetes 1.34 is finally here! A look back at K3s recent work and achievements 🥳

It's been a busy and productive few months, and we're excited to share some of the amazing progress we've made. From new features that make your lives easier to important bug fixes and foundational improvements, our team and community have been hard at work.

K3s is a lightweight Kubernetes distribution which excels in its deployment speed and minimal resource footprint. In fact, a lot of our users love K3s because it offers an unparalleled initialization speed.

While we have more detailed docs on setting up a High Availability (HA) cluster, this post will cover the simplest HA cluster you can create.