Kubernetes v1.31.0-alpha.3 has been built and pushed using Golang version 1.22.4.
The release notes have been updated in CHANGELOG-1.31.md, with a pointer to them on GitHub:
filename | sha512 hash |
---|---|
kubernetes.tar.gz | 81ee64c3ae9f3e528b79c933d9da60d3aae1a2c1a1a7378f273cfecadc6d86b8909f24cf5978aced864867de405c17f327e86d0c71c6e3f3e7add94eece310cd |
kubernetes-src.tar.gz | 269f41b1394f6531ac94fd83b18150380b7c6f0c79d46195a1191fbfd90a751582865f672d3b408e9d2b2cbc52d4d65e75d3faad1ec7144b8ddaa8a9b5f97fe6 |
filename | sha512 hash |
---|---|
kubernetes-client-darwin-amd64.tar.gz | 438a451916f27af8833fc7bc37e262736be418e7c2063eb70784a3b375962b2b7cbc6640cc7813a8d1a8b484bb4b9355b1862ca19461ca9fcebf4f1859e3e673 |
kubernetes-client-darwin-arm64.tar.gz | e2caa1e7248e8ff226afe6e2e3462617457ea00bee4b2f3ba83f859015e8315bcd5df4b4788f07e953f5e17d37e518b67da0d9288bb1ad351dd1dec9294431ea |
kubernetes-client-linux-386.tar.gz | 53b02b393dfcc111f1c3becc437593278704cb8e44855cf0d68f11996044be6b7da5d348c493d55829f340424c38559155c759dc75ec72893958e99a84a976a0 |
kubernetes-client-linux-amd64.tar.gz | 078233f079f0fcb73e5464995de716af999a3773c112834d2d3f711aff390bf0f8d1d2006c3bf7b53503ecd4757f51b02b33eabebd0b306469cf0d4353639325 |
kubernetes-client-linux-arm.tar.gz | 4214afa49d9fd177eb1cc9706b988962a6ff7ea1ac5e1c441f728b4076d6c02377c22d45ed50f497e2fe69ff767625c07150a5e41bbcab873811ec747293412f |
kubernetes-client-linux-arm64.tar.gz | 43482d72b2db2f76630981d8b21ab8a78cb23fb4ca4de1e5d8199634fc4935def3fa1493fa92c45ed387e204877b0305e066aa5bdf188f2018322128b9c836d7 |
kubernetes-client-linux-ppc64le.tar.gz | bba166df43a4c4b157ff469f1febc5c6e999655ebb63e05100db3b3f4b772234c5291458a12f013aa5f7af030957af1680434b89d4a78fb702254fe9e29b711d |
kubernetes-client-linux-s390x.tar.gz | 81e1464802062b0ceec6c52f3d43eae831109a07c37d6941d4f20767e9bba908e10f5f3e3bb8ab5efdcffbb45c62bad1f18430141c577e99a4c69540dd4e06f7 |
kubernetes-client-windows-386.tar.gz | e4f334c8bc0f3192f8aaf07c1b6ef94ce38ac150308fd0bfb27c1433dcba1543f0d56028a6ed4197c2ac8f9e2c650654549eb740ecabc2f2e671ebe6691d06f0 |
kubernetes-client-windows-amd64.tar.gz | 85df16f89541ac6a3e7b1b84b690c5255a09b22a7a8a0c4a0c1386edaeaf41a155b10f54d6fd5c096d57729979821180484ad869c2c7c31e650fcd6c1028d97a |
kubernetes-client-windows-arm64.tar.gz | 4656c8ed9c72425f077d059dc0cc9e3360893799fc79e98f25866411f7d25775f3cd1d9bbb0d10e690d319cb4dfa0839547704fae3dba77853ce36590d48f006 |
filename | sha512 hash |
---|---|
kubernetes-server-linux-amd64.tar.gz | 4b1c40bad5b6b4669b139a8956d51435d59111df19cc81c652eb2fcd1e1e9c850dec20b12e2f00f358bb5acc5ced2a6e7dc5e14cf8f063cca226cec55e2d3c19 |
kubernetes-server-linux-arm64.tar.gz | 23f6d045bbb914204dae109767879c5b58d389d8ebba6969b13e794d98a62c9b49fa7955f5ed6520063434779b3f316df9ee181943cf5a67146426c1b81b19bf |
kubernetes-server-linux-ppc64le.tar.gz | 16830cf5852f485f0a68cfa68c8fe505019d676e6b7e80783430cff29b9a8c9cf35aea6f2fb9de608b8a177964d7b49a9335eba8a6e11ec18725b3decea1dce8 |
kubernetes-server-linux-s390x.tar.gz | 8ba76e6c863cbb98e3179efcb23144ec367389c0735fe867df21fd3104945c869932684066b6009a906e3bf480ac7051a6b23c366adfd50591be93be9c6b2cf0 |
filename | sha512 hash |
---|---|
kubernetes-node-linux-amd64.tar.gz | 213c7692bbd980a4df2f5cff17d5688a0c635893ebdc27a11da4b40e97bb011caf0a4b7305600ff50d9e6e5d6b4daa31ccec2c90d171a72f97ecee0532316023 |
kubernetes-node-linux-arm64.tar.gz | f6a627b53d2f8ab7848eda49d69c68eb4a319e0a5721c34afb69858f2e25f9712cbf310626b4d58b0d9eed6464ee77b8eaad21e03cac4418b3659eebe4d35b11 |
kubernetes-node-linux-ppc64le.tar.gz | a25180775ae133d3c9278758d444e4934ec1b87c3b116fde03ff9e4249e3fca3c5135195a671614bb294e38f8e708ba5b77ba30fd763b634f47145c915d4dc8a |
kubernetes-node-linux-s390x.tar.gz | aea8682dcb0cf37c5c51e817691a44d8e058cda3977a79cad973638a5a77a3d554f90c7aa1c80b441b442d223c0e995ecc187e8c977ee6bb4cfd0768bc46ca21 |
kubernetes-node-windows-amd64.tar.gz | 2492217219ebf17574fba60aa612ab4adba0403f360a267657dd24092112ef7795302f255eb264ca36b0924c4bd527ade82d93ae65261f2856f512d9aa6a6104 |
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.
pod.spec.recourceClaims
array, the source
indirection is no longer necessary. Instead of e.g. source: resourceClaimTemplateName: my-template
, one can write resourceClaimTemplateName: my-template
. (#125116, @pohly) [SIG API Machinery, Apps, Auth, Node, Scheduling and Testing]api/v1
-like package structure. (#125162, @sttts) [SIG API Machinery and Apps]data
field. (#125549, @liggitt) [SIG API Machinery and Apps]fake.NewClientset()
instead of fake.NewSimpleClientset()
to create a clientset with managed field support. (#125560, @jpbetz) [SIG API Machinery, Auth, Instrumentation and Testing]WatchList
feature gate to Beta for kube-apiserver and enables WatchListClient
for KCM. (#125591, @p0lyn0mial) [SIG API Machinery and Testing].metadata.managedFields
field that self-requested informers of kube-apiserver doesn't need. (#124667, @linxiulei) [SIG API Machinery]KubeProxyDrainingTerminatingNodes
to stable (#125082, @alexanderConstantinescu) [SIG Network]spec.unhealthyPodEvictionPolicy
field has graduated to GA. This field may be set to AlwaysAllow
to always allow unhealthy pods covered by the PodDisruptionBudget to be evicted. (#123428, @atiratree) [SIG Apps, Auth, Node and Testing]DRA: using structured parameters with a claim that gets reused between pods may have led to a claim with an invalid state (allocated without a finalizer) which then caused scheduling of pods using the claim to stop. (#124931, @pohly) [SIG Node and Scheduling]
Fix a bug that Pods could stuck in the unschedulable pod pool if they're rejected by PreEnqueue plugins that could change its result by a change in resources apart from Pods.
DRA plugin is the only plugin that meets the criteria of the bug in in-tree, and hence if you have DynamicResourceAllocation
feature flag enabled, your DRA Pods could be affected by this bug. (#125527, @sanposhiho) [SIG Scheduling and Testing]
Fix bug where Server Side Apply causes spurious resourceVersion bumps on no-op patches to custom resources. (#125263, @jpbetz) [SIG API Machinery and Testing]
Fix bug where Server Side Apply causing spurious resourceVersion bumps on no-op patches containing empty maps. (#125317, @jpbetz) [SIG API Machinery and Testing]
Fix null lastTransitionTime in Pod condition when setting scheduling gate. (#122636, @lianghao208) [SIG Node and Scheduling]
Fix recursive LIST from watch cache returning object matching key (#125584, @serathius) [SIG API Machinery and Testing]
Fix: during the kube-controller-manager restart, when the corresponding Endpoints resource was manually deleted and recreated, causing the endpointslice to fail to be created normally. (#125359, @yangjunmyfm192085) [SIG Apps and Network]
Kube-apiserver: fixes a 1.27+ regression watching a single namespace via the deprecated /api/v1/watch/namespaces/$name endpoint where watch events were not delivered after the watch was established (#125145, @xyz-li) [SIG API Machinery, Node and Testing]
Kube-apiserver: timeouts configured for authorization webhooks in the --authorization-config file are now honored, and webhook timeouts are accurately reflected in webhook metrics with result=timeout (#125552, @liggitt) [SIG API Machinery, Auth and Testing]
Kubeadm: Added --yes
flag to the list of allowed flags so that it can be mixed with kubeadm upgrade apply --config
(#125566, @xmudrii) [SIG Cluster Lifecycle]
Kubeadm: during the validation of existing kubeconfig files on disk, handle cases where the "ca.crt" is a bundle and has intermediate certificates. Find a common trust anchor between the "ca.crt" bundle and the CA in the existing kubeconfig on disk instead of treating "ca.crt" as a file containing a single CA. (#123102, @astundzia) [SIG Cluster Lifecycle]
Kubeadm: fix a bug where the path of the manifest can not be specified when kubeadm upgrade diff
specified a config file, and the --api-server-manifest
, --controller-manager-manifest
and --scheduler-manifest
flags of kubeadm upgrade diff
are marked as deprecated and will be removed in a future release. (#125779, @SataQiu) [SIG Cluster Lifecycle]
Kubeadm: the --feature-gates
flag is deprecated and no-op for kubeadm upgrade apply/plan
, and it will be removed in a future release. The upgrade workflow is not designed to reconfigure the cluster. Please edit the 'featureGates' field of ClusterConfiguration which is defined in the kube-system/kubeadm-config ConfigMap instead. (#125797, @SataQiu) [SIG Cluster Lifecycle]
Kubelet now hard rejects pods with AppArmor if the node does not have AppArmor enabled. (#125776, @vinayakankugoyal) [SIG Node]
Now the .status.ready field is tracked faster when active Pods are deleted, specifically when Job is failed, gets suspended or has too many active pods (#125546, @dejanzele) [SIG Apps]
When schedulingQueueHint is enabled, the scheduling queue doesn't update Pods being scheduled immediately. (#125578, @nayihz) [SIG Scheduling]
--enable-logs-handler
flag and log-serving functionality which was already deprecated is now switched off by default and scheduled to be removed in v1.33. (#125787, @dims) [SIG API Machinery, Network and Testing]validateSupportedVersion
to include the checked resource kind name. (#125758, @SataQiu) [SIG Cluster Lifecycle]kubectl describe service
now shows internal traffic policy and ip mode of load balancer IP (#125117, @tnqn) [SIG CLI and Network]Nothing has changed.
Contributors, the CHANGELOG-1.31.md has been bootstrapped with v1.31.0-alpha.3 release notes and you may edit now as needed.
Published by your Kubernetes Release Managers.
🎉
--
You received this message because you are subscribed to the Google Groups "dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/CAKC1YU0S8WM%2BcDVKgw8RVzRHMwFehi41i5cyp2LepAsDe3DejA%40mail.gmail.com.