k3s | v1.36.4+k3s1

k3s v1.36.4+k3s1 released on 27-08-2026


k3s v1.36.4+k3s1 is out now. Operators get Kubernetes v1.36.4, a rebuild with Go 1.26.7 and a set of component and runtime bumps focused on security, compatibility and stability.

Check the k3s GitHub release and the upstream Kubernetes and Traefik changelogs, or the k3s documentation, for full details and upgrade instructions.

What’s in this release

  • Kubernetes updated to v1.36.4 and k3s rebuilt with Go 1.26.7, including upstream fixes referenced in the Kubernetes changelog.
  • Traefik Helm chart upgraded to v40.x; the ingress-nginx migration includes a breaking change where the provider name changes from kubernetesIngressNginx to kubernetesIngressNGINX.
  • Embedded component and runtime bumps including containerd v2.3.4-k3s1.36, Local-path-provisioner v0.0.37, a mirrored CoreDNS image update, and updates to Kine, Etcd, runc, Flannel, Metrics-server, Traefik and Helm-controller.

Upgrade notes

  • Breaking change: Traefik chart v40.x renames the ingress-nginx provider from kubernetesIngressNginx to kubernetesIngressNGINX — review Traefik and Ingress configuration and follow the Traefik chart v40.0.0 migration notes.
  • If you cannot migrate immediately, remain on the previous k3s release (v1.36.3+k3s1) or use a Traefik chart version prior to v40.x; report issues on the k3s GitHub or ask for help on the Rancher Slack.

Share your experience with the upgrade — report problems or tips on the k3s GitHub issue tracker or in the Rancher Slack so others can benefit.

Related posts

k3s | v1.36.4+k3s1

k3s update: Kubernetes and Go bumps, Traefik chart renames kubernetesIngressNginx to kubernetesIngressNGINX, component updates and maintenance

k3s | v1.36.4+k3s1

k3s v1 36 4 k3s1: Kubernetes v1 36 4 and Go 1 26 7, Traefik chart v40 and ingress nginx provider rename, embedded component bumps, test in staging

n8n | n8n@2.36.8

n8n 2 36 8: Fixes domain restricted credential bug so nodes can use credentials scoped to domain, no breaking changes, upgrade if you use domain restrictions