Kubernetes v1.32.0-rc.0 has been built and pushed using Golang version 1.23.3.
The release notes have been updated in CHANGELOG-1.32.md, with a pointer to them on GitHub:
filename | sha512 hash |
---|---|
kubernetes.tar.gz | eaa85d26d9315bfe43b2d0e25c317c6a756b031f9c63b14ab1c06a1970b9e2498ecde4dc6c431b926f1b700c02f232e8b63a4e1e02cd3af8cba45a140feba002 |
kubernetes-src.tar.gz | c7589b72811610703d7ac405f6cbfc20d319015f09a0dc9809bc88db706c95eca2b1329be45f370b185e346393aef823f50dc79a5a7151ba6ca168e7ffbd3b09 |
filename | sha512 hash |
---|---|
kubernetes-client-darwin-amd64.tar.gz | 6294ea5125483ae5c9273a29cff85cdd2322f1ca240f6f3eb03455314d01c55b1869a4d6ff496522b5b76823760cad28c786ca528883bc54b3cdb4e85c5063c8 |
kubernetes-client-darwin-arm64.tar.gz | 4ba6e849650b19a3bf98ff978b26bb6ff2c5539aeb6766048b2fb36c5fce98d84f482607230df43553263d7def611e467dfdaac64282b99d59d585eb54878d33 |
kubernetes-client-linux-386.tar.gz | fe2aa6e4b8aa963b37b19fbe4c235e5e19c1c374da6b33723d36081bc5e13348a9ba4c2ceb01b4729a514995e9f3ff8dbe8c34576b3620634dfc15e7031dcda6 |
kubernetes-client-linux-amd64.tar.gz | 38a9c36075c1f75cf9dc36dedd1d4d7c37dc5f7d012d427ebaebee2b7a54a816aac73d6054e936f4168b272156975b4addec2224902bd15bf64b74885b6d3a86 |
kubernetes-client-linux-arm.tar.gz | 05f76c05874aee0b1c76c0be855efd1e56241b3cd8b1ae371856052a85de2fed69705438cefd616e85e7d2af512882a7de7fb5cb065f1b14b1877bb4bc5552db |
kubernetes-client-linux-arm64.tar.gz | 2021324d205a091d1c06cf913dc7207d322e9a6fb4b5befa453ecaf740e6438ed1ed7f81c8140e78ac1d5e69f657af13fe0c1334f3adafebf7fcec9996d6bbe2 |
kubernetes-client-linux-ppc64le.tar.gz | 87bee10e358781a63345d67f86184a2702ee9fa9cd81b6647fc852b56160a28faf3c008c7a43ca78cc5d675b23d4952f4ca64382fe16930313eec2d381ddc636 |
kubernetes-client-linux-s390x.tar.gz | 734d62b86165aeda36a994b7493a8514565d3ad12fea67fff231d161021fbeddbf1e694c18f597a4f873b00fc2d0d2c2d6e1a60f74714fb9959d4989e5e94f31 |
kubernetes-client-windows-386.tar.gz | 80faf17e8aebbf682f577cac4968dd472108ce6f9f16ecc8167fa13d6a31928fb4f87ba51fe2becabea73296dbd2b7a551dded4d4f172066576533c3eda46d78 |
kubernetes-client-windows-amd64.tar.gz | f97ca8359f4c466d43bbc824f508ea8668f00a73f348abaf4b08743d7c7ac05624b927f1a572f7f11f28861c9bf4f7d4c37c052e57c360062b529791603e820f |
kubernetes-client-windows-arm64.tar.gz | a26953011fbd955fd9a8faeaa350a44b42e7adb99daf4ba0eaa7f738c2c4ddbb1d43f8f09b80926e1239466d81340978dd70f8a4657847059e074cc801bf9267 |
filename | sha512 hash |
---|---|
kubernetes-server-linux-amd64.tar.gz | 9e9a615e67971410ca4094e3521908cc929f40a38a7939cec09411f80e6b6d34273af3f5a9e18b3cc3e4b9a94cea4ffb414581c25a9d61d905e9dc1d98bd0e15 |
kubernetes-server-linux-arm64.tar.gz | 352d53b50b0931cf8f9e447de26aa00cbdb4883104ef769264bf1068b65fc7997f8fce19b97145c0288894791f724f7048c220dd08589393d713c527cc23ed75 |
kubernetes-server-linux-ppc64le.tar.gz | 3b675db6bc25b36e1be5f753d7e37c44062ed04d06303461919fa42ea1ac1a5b65ee90f081db2095086e5f7a5bc5ba875feca76da5bbf1a7d0de56e351de07e9 |
kubernetes-server-linux-s390x.tar.gz | 9871b11b070edbe28d9aee8ee75079a748ac0b82f7f8e65cfcbdc078730585111eb437762d152c7a2d7be883e4c89edcbc9e036559316fd32361571be082df9e |
filename | sha512 hash |
---|---|
kubernetes-node-linux-amd64.tar.gz | daa150e2b95822f9444fd278c2561f14b55ae69bf34c442c7aee52a48979dbb61a14da476a9d0aaa17ab557a46b75eea43342b173f001c1d04a520bae9ea2c2b |
kubernetes-node-linux-arm64.tar.gz | 57166c47374c28b7c3ad0214edc98a252f1f3b5390cd2d4ad9a043bc5ed7a5819d1e5503607277492b7a1d405ace3a06d9803464018790a3a761368184230241 |
kubernetes-node-linux-ppc64le.tar.gz | a077fcf0579f4631fca7a07f7a972971bdf29f46faca2a96de84c036a237b1523306c9aa46e395d11c1fc18bde8d9700c87ca658c4e3abd4be75ec231ad72c42 |
kubernetes-node-linux-s390x.tar.gz | 452721c3c39d6800d335a5f4cbd672f8cf52555c97850497530951e979a742fcb045963e7d7b88ad436f258bda1ee42b8fbc3cad57dc9f5ff92f55be4edc0ae6 |
kubernetes-node-windows-amd64.tar.gz | f09db4e3c81b8dea49d05efa7de6f5ac2c783c93b22f939707811a3f295c770a8b900cd83d91a3fda37c01b22d2c39e6c7710d3f8fad3d4ffc8d1117dd7b09e1 |
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.
--feature-gates=AllowUnsafeMalformedObjectDeletion=true
.
It comes with an API change, a new delete option ignoreStoreReadErrorWithClusterBreakingPotential
has
been introduced, it is not set by default, this maintains backward compatibility.
In order to perform an unsafe deletion of a corrupt resource, the user must enable the option for the delete
request. A resource is considered corrupt if it can not be successfully retrieved from the storage due to
a) transformation error e.g. decryption failure, or b) the object failed to decode. Normal deletion flow is
attempted first, and if it fails with a corrupt resource error then it triggers unsafe delete.
In addition, when this feature is enabled, the 'details' field of 'Status' from the LIST response
includes information that identifies the corrupt object(s).
NOTE: unsafe deletion ignores finalizer constraints, and skips precondition checks.
WARNING: this may break the workload associated with the resource being unsafe-deleted, if it relies on
the normal deletion flow, so cluster breaking consequences apply. (#127513, @tkashem) [SIG API Machinery, Etcd, Node and Testing]Stream
field to PodLogOptions
, which allows clients to request certain log stream(stdout or stderr) of the container.
Please also note that the combination of a specific Stream
and TailLines
is not supported. (#127360, @knight42) [SIG API Machinery, Apps, Architecture, Node, Release and Testing]singleProcessOOMKill
flag to the kubelet configuration. Setting that to true enable single process OOM killing in cgroups v2. In this mode, if a single process is OOM killed within a container, the remaining processes will not be OOM killed. (#126096, @utam0k) [SIG API Machinery, Node, Testing and Windows]SchedulerAsyncPreemption
feature gate is enabled, the scheduler now runs API calls to trigger preemptions asynchronously for better performance. (#128170, @sanposhiho) [SIG Scheduling and Testing]CrashLoopBackOff
. To set this for a node, turn on the feature gate KubeletCrashLoopBackoffMax
and set the CrashLoopBackOff.MaxContainerRestartPeriod
field between "1s"
and "300s"
in your kubelet config file. (#128374, @lauralorenz) [SIG API Machinery and Node]resources
at spec
level for pod-level resources. (#128407, @ndixita) [SIG API Machinery, Apps, CLI, Cluster Lifecycle, Node, Release, Scheduling and Testing]MutatingAdmissionPolicy
feature gate and the admissionregistration.k8s.io/v1alpha1
API via --runtime-config
. (#127134, @jpbetz) [SIG API Machinery, Auth, Etcd and Testing]ServiceAccountNodeAudienceRestriction
that's enabled by default. (#128077, @aramase) [SIG Auth, Storage and Testing]StatefulSetAutoDeletePVC
from beta to stable. (#128247, @mattcary) [SIG API Machinery, Apps, Auth and Testing]BtreeWatchCache
feature gate. (#128415, @serathius) [SIG API Machinery, Auth and Cloud Provider]InPlacePodVerticalScalingExclusiveCPUs
defaults to false
, but can be enabled to unblock development on (#127262, @tallclair) [SIG Node]. (#128287, @esotsal) [SIG Node, Release and Testing]SchedulerQueueingHints
to beta; the feature gate is now enabled by default. (#128472, @sanposhiho) [SIG Scheduling]ExternalServiceAccountTokenSigner
feature gate and specifying --service-account-signing-endpoint
. The flag value can either be the location of a Unix domain socket on a filesystem, or be prefixed with an @ symbol and name a Unix domain socket in the abstract socket namespace. (#128190, @HarshalNeelkamal) [SIG API Machinery, Apps, Auth, Etcd, Instrumentation, Node, Release and Testing]NodeLocalCRISocket
. When the feature gate is enabled, kubeadm will generate the /var/lib/kubelet/instance-config.yaml
file to customize the containerRuntimeEndpoint
field in the kubelet configuration for each node and will not write the same CRI socket on the Node object as an annotation. (#128031, @HirazawaUi) [SIG Cluster Lifecycle]kubernetes.io/kube-apiserver-serving
X.509 certificate signer. This ClusterTrustBundle contains a PEM bundle in its payload that you can use to verify kube-apiserver serving certificates. (#127326, @stlaz) [SIG API Machinery, Apps, Auth, Cluster Lifecycle and Testing]image
volume source type, It passes the missing mount attributes to the CRI implementation, including readOnly
, propagation
, and recursiveReadOnly
. When the readOnly field of the containerMount is explicitly set to false, the kubelet will take the readOnly
as true to the CRI implementation because the image volume plugin requires the mount to be read-only.image
volume source type is used and mounted to /etc/hosts
in the container. (#126806, @carlory) [SIG Node and Storage]StartupProbe
is stopped explicity when successThrethold
is reached.
This eliminates the problem that StartupProbe
is executed more than successThrethold
. (#121206, @mochizuki875) [SIG Node]--runonce
mode.
If you specify the kubelet command line flag --runonce
, this is an error.
Setting runOnce
in a kubelet configuration file is also an error, and specifying any
value for that configuration option is now deprecated. (#126336, @HirazawaUi) [SIG Node and Scalability]Nothing has changed.
Contributors, the
CHANGELOG-1.32.md has been bootstrapped with
v1.32.0-rc.0 release notes and you may edit now as needed.
Published by your
Kubernetes Release
Managers.