Bump kubernetes from 30.1.0 to 31.0.0 in /src

[dependabot]

Bumps kubernetes from 30.1.0 to 31.0.0.

Release notes

Sourced from kubernetes's releases.

Kubernetes Python Client v31.0.0 Stable Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v31.0.0.zip
cd client-python-v31.0.0
python setup.py install

Then follow examples in https://github.com/kubernetes-client/python/tree/release-31.0/examples

Changelog: https://github.com/kubernetes-client/python/blob/release-31.0/CHANGELOG.md

Kubernetes Python Client v31.0.0 Beta 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v31.0.0b1.zip
cd client-python-v31.0.0b1
python setup.py install

Then follow examples in https://github.com/kubernetes-client/python/tree/release-31.0/examples

Changelog: https://github.com/kubernetes-client/python/blob/release-31.0/CHANGELOG.md

Kubernetes Python Client v31.0.0 Alpha 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v31.0.0a1.zip
cd client-python-v31.0.0a1
</tr></table> 

... (truncated)

Changelog

Sourced from kubernetes's changelog.

v31.0.0

Kubernetes API Version: v1.31.0

v31.0.0b1

Kubernetes API Version: v1.31.0

v31.0.0a1

Kubernetes API Version: v1.31.0

API Change

• 'ACTION REQUIRED: The Dynamic Resource Allocation (DRA) driver's DaemonSet must be deployed with a service account that enables writing ResourceSlice and reading ResourceClaim objects.' (kubernetes/kubernetes#125163, @​pohly) [SIG Auth, Node and Testing]
• Add UserNamespaces field to NodeRuntimeHandlerFeatures (kubernetes/kubernetes#126034, @​sohankunkerkar) [SIG API Machinery, Apps and Node]
• Added Coordinated Leader Election as Alpha under the CoordinatedLeaderElection feature gate. With the feature enabled, the control plane can use LeaseCandidate objects (coordination.k8s.io/v1alpha1 API group) to participate in a leader election and let the kube-apiserver select the best instance according to some strategy. (kubernetes/kubernetes#124012, @​Jefftree) [SIG API Machinery, Apps, Auth, Cloud Provider, Etcd, Node, Release, Scheduling and Testing]
• Added a .status.features.supplementalGroupsPolicy field to Nodes. The field is true when the feature is implemented in the CRI implementation (KEP-3619). (kubernetes/kubernetes#125470, @​everpeace) [SIG API Machinery, Apps, Node and Testing]
• Added an allocatedResourcesStatus to each container status to indicate the health status of devices exposed by the device plugin. (kubernetes/kubernetes#126243, @​SergeyKanzhelev) [SIG API Machinery, Apps, Node and Testing]
• Added support to the kube-proxy nodePortAddresses / --nodeport-addresses option to accept the value "primary", meaning to only listen for NodePort connections on the node's primary IPv4 and/or IPv6 address (according to the Node object). This is strongly recommended, if you were not previously using --nodeport-addresses, to avoid surprising behavior. (This behavior is enabled by default with the nftables backend; you would need to explicitly request --nodeport-addresses 0.0.0.0/0,::/0 there to get the traditional "listen on all interfaces" behavior.) (kubernetes/kubernetes#123105, @​danwinship) [SIG API Machinery, Network and Windows]
• Added the feature gates StrictCostEnforcementForVAP and StrictCostEnforcementForWebhooks to enforce the strict cost calculation for CEL extended libraries. It is strongly recommended to turn on the feature gates as early as possible. (kubernetes/kubernetes#124675, @​cici37) [SIG API Machinery, Auth, Node and Testing]
• Changed how the API server handles updates to .spec.defaultBackend of Ingress objects. Server-side apply now considers .spec.defaultBackend to be an atomic struct. This means that any field-owner who sets values in that struct (they are mutually exclusive) owns the whole struct. For almost all users this change has no impact; for controllers that want to change the default backend port from number to name (or vice-versa), this makes it easier. (kubernetes/kubernetes#126207, @​thockin) [SIG API Machinery]
• Component-base/logs: when compiled with Go >= 1.21, component-base will automatically configure the slog default logger together with initializing klog. (kubernetes/kubernetes#120696, @​pohly) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Storage and Testing]
• CustomResourceDefinition objects created with non-empty caBundle fields which are invalid or do not contain any certificates will not appear in discovery or serve endpoints until a valid caBundle is provided. Updates to CustomResourceDefinition are no longer allowed to transition a valid caBundle field to an invalid caBundle field, because this breaks serving of the existing CustomResourceDefinition. (kubernetes/kubernetes#124061, @​Jefftree) [SIG API Machinery]
• Dynamic Resource Allocation (DRA): Added a feature so the number of ResourceClaim objects can be limited per namespace and by the number of devices requested through a specific class via the v1.ResourceQuota mechanism. (kubernetes/kubernetes#120611, @​pohly) [SIG API Machinery, Apps, Auth, CLI, Etcd, Node, Release, Scheduling and Testing]
• Dynamic Resource Allocation (DRA): client-side validation of a ResourceHandle would have accepted a missing DriverName, whereas server-side validation then would have raised an error. (kubernetes/kubernetes#124075, @​pohly)
• Dynamic Resource Allocation (DRA): in the 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. (kubernetes/kubernetes#125116, @​pohly) [SIG API Machinery, Apps, Auth, Node, Scheduling and Testing]
• Enhanced the Dynamic Resource Allocation (DRA) with an updated version of the resource.k8s.io API group. The primary user-facing type remains the ResourceClaim, however significant changes have been made, resulting in the new version, v1alpha3, which is not compatible with the previous version. (kubernetes/kubernetes#125488, @​pohly) [SIG API Machinery, Apps, Auth, CLI, Cluster Lifecycle, Etcd, Node, Release, Scheduling, Storage and Testing]
• Fixed a 1.30.0 regression in OpenAPI descriptions of the imagePullSecrets and hostAliases fields to mark the fields used as keys in those lists as either defaulted or required. (kubernetes/kubernetes#124553, @​pmalek)
• Fixed a 1.30.0 regression in openapi descriptions of PodIP.IP and HostIP.IP fields to mark the fields used as keys in those lists as required. (kubernetes/kubernetes#126057, @​thockin)
• Fixed a bug in the API server where empty collections of ValidatingAdmissionPolicies did not have an items field. (kubernetes/kubernetes#124568, @​xyz-li) [SIG API Machinery]
• Fixed a deep copy issue when retrieving the controller reference. (kubernetes/kubernetes#124116, @​HiranmoyChowdhury) [SIG API Machinery and Release]
• Fixed code-generator client-gen to work with api/v1-like package structure. (kubernetes/kubernetes#125162, @​sttts) [SIG API Machinery and Apps]
• Fixed incorrect "v1 Binding is deprecated in v1.6+" warning in kube-scheduler log. (kubernetes/kubernetes#125540, @​pohly) [SIG API Machinery]
• Fixed the comment for the Job's managedBy field. (kubernetes/kubernetes#124793, @​mimowo) [SIG API Machinery and Apps]
• Fixed the documentation for the default value of the procMount entry in securityContext within a Pod. The documentation was previously using the name of the internal variable DefaultProcMount, rather than the actual value, "Default". (kubernetes/kubernetes#125782, @​aborrero) [SIG Apps and Node]
• Graduate PodDisruptionConditions to GA and lock (kubernetes/kubernetes#125461, @​mimowo) [SIG Apps, Node, Scheduling and Testing]

... (truncated)

Commits

• bc8c691 Merge pull request #2281 from yliaog/automated-release-of-31.0.0-upstream-rel...
• dbdba2b Fixed CHANGELOG, the API version should be 1.31.0, the release tooling
• 365dbaf Update the compatibility matrix and maintenance status
• 77a9bd0 generated client change
• a15ecb1 update changelog
• 173931a update version constants for 31.0.0 release
• d8ee677 Merge pull request #2277 from yliaog/automated-release-of-31.0.0b1-upstream-r...
• 7abc423 updated compatibility matrix and maintenance status
• 2be6881 generated client change
• e49c89a update changelog
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ChristianGeie]

@dependabot recreate

[ChristianGeie]

LGTM