Kubernetes v1.33.12 is live!

23 views
Skip to first unread message

Nabarun Pal

unread,
May 12, 2026, 12:45:50 PM (yesterday) May 12
to kubernete...@googlegroups.com, dev
Kubernetes Community,

Kubernetes v1.33.12 has been built and pushed using Golang version 1.25.9.

The release notes have been updated in CHANGELOG-1.33.md, with a pointer to them on GitHub:


v1.33.12

Downloads for v1.33.12

Source Code

filename sha512 hash
kubernetes.tar.gz 571f93b7ee94d20f3df321877a79729318550c1de5c29f2e64261e519bafd89cede94d04531de0fe47ae9311e548d10bc3e5c735164723f351433b7079b54b11
kubernetes-src.tar.gz 330d39f284d7d8445d146839be12e2a7a9ca2316cd188b99f6de29e8538b104249ca3e701c53c8222bd7450c10a2ac3737f9726562dd11842c9c59262e10c838

Client Binaries

filename sha512 hash
kubernetes-client-darwin-amd64.tar.gz dc42de25b634e159fde038b0468e792cd25f8213076da70ef1c667b57080062e3fd28b590f6cc5627047acd6d6305e4205ca293f80e229a4ff8ba4022b29eb62
kubernetes-client-darwin-arm64.tar.gz 4979472ce2b433d0f570ec00ccabb7a16d7ad0b7dd5c181d79a71bb13e8396cfaaa3309999ea0f047776d1de9be24f17cc7d8b6c62ff5f4eb6a1e314155b9072
kubernetes-client-linux-386.tar.gz 75ad611c138257d61229a8e8df6ea792dc2eeb716a491af5f0bf6e5ef446df017f405d74ad985eac9d0d127f603d238c426ec7841a35f78f01d2408436e05fbe
kubernetes-client-linux-amd64.tar.gz 8f22f89becdbcb89830b8bba894b3403df50951fb657926987933bdf01034b9b817495005cd29c79d242338c233a4fdc4f216e1a20bba3786b05f0549cf919c4
kubernetes-client-linux-arm.tar.gz 6d5421bd6e651dd263cc003b5af394be868f9dc12a6ead18d8cee8f7a4f9b36096ee32c68162772720f7bac5bd8d0bad5e277b856a97d030abd37ce8fa7d4d22
kubernetes-client-linux-arm64.tar.gz 53cab31dda940acb92cd3e2000186001b5336cc225f4b04e2b19112d17aac56662a50cda0a24999ba1764dd4851f1d123c04bfecb96f05da739cf0311acba71d
kubernetes-client-linux-ppc64le.tar.gz e15856dbf1eb8b2489d49f9782deea73287c6a6ece9290b8be1e0de439842bed87f77dd9db0e2e84309645cf23f233de9a9af235ad054b3052425d27d8709d38
kubernetes-client-linux-s390x.tar.gz 7d9383f4cac92af5e4eaaf9d5828cc50dbd43abdd4fee3f42a31412152311a214bc050e70d0c208f5c64d736ee8bddacf4660329ceab94f596ff89173fea6b28
kubernetes-client-windows-386.tar.gz b7e642bd0259c4fa946993920057c5e39721705ba4de6dceebe5e0d1ff99d59afd0468ce0d8009e81a89ead53791c688e713c04c9192b406a8acb0f2434bc7dd
kubernetes-client-windows-amd64.tar.gz 4866742d04735e4005706135dfe82215fd80347c3a09c8ab5a9a73f1ced83f4b92eb37deae54d3946e7a63d91aea6a66770fc08578f8db269f130da14dd6043e
kubernetes-client-windows-arm64.tar.gz c3bff4e6b487da2743c6bd6a5043293d52ee6cbbb4da3c491104d97c3adf36c1e766b1e9099ee44811e38845b4104ea89a9758cd2810d9e6857d6e9fc2bb9594

Server Binaries

filename sha512 hash
kubernetes-server-linux-amd64.tar.gz 5c94d29c09591c151ae9746e06631656190498a2e97cc6e5f7ccd989d529f7f531b67c4d734bf7e4191bcedc650b32d3035d9e33e4e1053eb6ffb7303c78f94f
kubernetes-server-linux-arm64.tar.gz f22df0293bdc5c261d1c6c3af6fbea2f8d16756807b088d9bfa82f476ce17fe85880e5f46e4aaccb9fe93dc871b9ba1354d0d064804b6214b91b1b9161629a73
kubernetes-server-linux-ppc64le.tar.gz b5903f4b248091d0b7ef21f71e75446e65f5c17767e77de3a8e83e1d81dc468a7089bb590f7440468669905b13207264ad5cb74c941b99c46bc87ff471cf6e30
kubernetes-server-linux-s390x.tar.gz f71bdecf78177793209b002a2057e8e796ed4366898ba85a7c18e372639fc557017857ee1a9d565f8b050bddfd6bfd75d487d452ddf2c38b18e00ef795f130b4

Node Binaries

filename sha512 hash
kubernetes-node-linux-amd64.tar.gz dd9b956943584a5015dd9bde7cd7466affaaed9f96a84b4247895e92effb2cb082c44e6b6d482f2408aa9d6394ac83a10b2690040c3c5a47cac364faf43c6b77
kubernetes-node-linux-arm64.tar.gz 3a8684de7400641e0080a0c8ae05b3f8a405185eee3a7e40eed63ff6d2ff0e59e19059a7f42258a984972cb1513665b19668c4cb8c2b5b65370608af5f3229ca
kubernetes-node-linux-ppc64le.tar.gz b284c2e7f53387fb4dcdc201021ec4d5eeb287d52b4f1e8bff04c8248e15ab6906f7a0c4c776218065869a9d085dca8f749db169aff456bdbb1e987af3c18454
kubernetes-node-linux-s390x.tar.gz 76c144b0ecf8a455b513c787b33cf0cd32eba6b8e88de04c9cf0c31d00e51586ffc5b722597bc4713d6718c6400c3e2dbd55db2e67760151fe10b0ac74ded798
kubernetes-node-windows-amd64.tar.gz 7f45d89d8d2018017880f37c44d2dc278844e40a6bef2a7b0f3d3d2731099e4a92ad86a05f0d2204fb3c8765ef987978138554ff6558799e6a97de03d1be3da7

Container Images

All container images are available as manifest lists and support the described architectures. It is also possible to pull a specific architecture directly by adding the "-$ARCH" suffix to the container image name.

name architectures
registry.k8s.io/conformance:v1.33.12 amd64, arm64, ppc64le, s390x
registry.k8s.io/kube-apiserver:v1.33.12 amd64, arm64, ppc64le, s390x
registry.k8s.io/kube-controller-manager:v1.33.12 amd64, arm64, ppc64le, s390x
registry.k8s.io/kube-proxy:v1.33.12 amd64, arm64, ppc64le, s390x
registry.k8s.io/kube-scheduler:v1.33.12 amd64, arm64, ppc64le, s390x
registry.k8s.io/kubectl:v1.33.12 amd64, arm64, ppc64le, s390x

Changelog since v1.33.11

Changes by Kind

Bug or Regression

  • Kubeadm: during 'kubeadm init', if the default 'admin.conf' and 'super-admin.conf' paths are used, load the files, but construct in memory kubeconfigs that point to the InitConfiguration.localAPIEndpoint instead of the ClusterConfiguration.controlPlaneEndpoint. This would resolve issues with delayed load balancers which are provisioned only after the first kube-apiserver instance starts. (#138686, @neolit123) [SIG Cluster Lifecycle]
  • Kubeadm: skip LocalAPIEndpoint defaulting on 'kubeadm join' for worker nodes. (#138805, @neolit123) [SIG Cluster Lifecycle]
  • Kubeadm: use a dedicated ClusterRole 'system:kubelet-api-admin' for the kube-apiserver kubelet client. (#138964, @neolit123) [SIG Cluster Lifecycle]
  • Kubeadm: when checking the etcd cluster status use a quorum approach, instead of considering the health of all members. This would allow the check to not fail if there are sufficient healthy voting members. (#138541, @ahrtr) [SIG Cluster Lifecycle]

Dependencies

Added

Nothing has changed.

Changed

Nothing has changed.

Removed

Nothing has changed.



Contributors, the CHANGELOG-1.33.md has been bootstrapped with v1.33.12 release notes and you may edit now as needed.



Published by your Kubernetes Release Managers.


Reply all
Reply to author
Forward
0 new messages