chore(deps): bump kubernetes from 31.0.0 to 32.0.0

[dependabot]

Bumps kubernetes from 31.0.0 to 32.0.0.

Release notes

Sourced from kubernetes's releases.

Kubernetes Python Client v32.0.0 Stable Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

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

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

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

Kubernetes Python Client v32.0.0 Beta 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

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

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

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

Kubernetes Python Client v32.0.0 Alpha 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

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

... (truncated)

Changelog

Sourced from kubernetes's changelog.

v32.0.0

Kubernetes API Version: v1.32.1

Bug or Regression

• Fixed PortForward proxy to close local Python sockets when the WebSocket closes. (#2316, @​anvilpete)

v32.0.0b1

Kubernetes API Version: v1.32.1

API Change

• DRA API: the maximum number of pods which can use the same ResourceClaim is now 256 instead of 32. Beware that downgrading a cluster where this relaxed limit is in use to Kubernetes 1.32.0 is not supported because 1.32.0 would refuse to update ResourceClaims with more than 32 entries in the status.reservedFor field. (kubernetes/kubernetes#129544, @​pohly) [SIG API Machinery, Node and Testing]
• NONE (kubernetes/kubernetes#129598, @​aravindhp) [SIG API Machinery and Node]

v32.0.0a1

Kubernetes API Version: v1.32.0

API Change

• ACTION REQUIRED for custom scheduler plugin developers: PodEligibleToPreemptOthers in the preemption interface now includes ctx in the parameters. Please update your plugins' implementation accordingly. (kubernetes/kubernetes#126465, @​googs1025) [SIG Scheduling]
• Changed NodeToStatusMap from a map to a struct and exposed methods to access the entries. Added absentNodesStatus, which informs the status of nodes that are absent in the map. For developers of out-of-tree PostFilter plugins, ensure to update the usage of NodeToStatusMap. Additionally, NodeToStatusMap should eventually be renamed to NodeToStatusReader. (kubernetes/kubernetes#126022, @​macsko) [SIG Node, Scheduling, and Testing]
• A new /resize subresource was added to request pod resource resizing. Update your k8s client code to utilize the /resize subresource for Pod resizing operations. (kubernetes/kubernetes#128266, @​AnishShah) [SIG API Machinery, Apps, Node and Testing]
• A new feature that allows unsafe deletion of corrupt resources has been added, it is disabled by default, and it can be enabled by setting the option --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. (kubernetes/kubernetes#127513, @​tkashem) [SIG API Machinery, Etcd, Node and Testing]
• Added 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. (kubernetes/kubernetes#126096, @​utam0k) [SIG API Machinery, Node, Testing and Windows]
• Added a /flagz endpoint for kube-apiserver endpoint. (kubernetes/kubernetes#127581, @​richabanker) [SIG API Machinery, Architecture, Auth and Instrumentation]
• Added a 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. (kubernetes/kubernetes#127360, @​knight42) [SIG API Machinery, Apps, Architecture, Node, Release and Testing]
• Added alpha support for asynchronous Pod preemption. When the SchedulerAsyncPreemption feature gate is enabled, the scheduler now runs API calls to trigger preemptions asynchronously for better performance. (kubernetes/kubernetes#128170, @​sanposhiho) [SIG Scheduling and Testing]
• Added driver-owned fields in ResourceClaim.Status to report device status data for each allocated device. (kubernetes/kubernetes#128240, @​LionelJouin) [SIG API Machinery, Network, Node and Testing]
• Added enforcement of an upper cost bound for DRA evaluations of CEL. The API server and scheduler now enforce an upper bound on the cost and runtime steps required for evaluating a CEL expression. (kubernetes/kubernetes#128101, @​pohly) [SIG API Machinery and Node]
• Added the ability to change the maximum backoff delay accrued between container restarts for a node for containers in 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. (kubernetes/kubernetes#128374, @​lauralorenz) [SIG API Machinery and Node]
• Allow for Pod search domains to be a single dot . or contain an underscore _ (kubernetes/kubernetes#127167, @​adrianmoisey) [SIG Apps, Network and Testing]
• Annotation batch.kubernetes.io/cronjob-scheduled-timestamp added to Job objects scheduled from CronJobs is promoted to stable. (kubernetes/kubernetes#128336, @​soltysh)

... (truncated)

Commits

• 8980f12 Merge pull request #2331 from yliaog/automated-release-of-32.0.0-upstream-rel...
• 8db4744 updated compatibility matrix and maintenance status
• b9091e3 generated client change
• dbedb4d update version constants for 32.0.0 release
• 0d9f4f8 update changelog with release notes from master branch
• 2af3cf3 Close the Python sockets when the Websocket closes
• 96f3758 Merge pull request #2323 from yliaog/automated-release-of-32.0.0b1-upstream-r...
• fc8b2b6 updated compatibility matrix and maintenance status
• b42b60c generated client change
• 43b6175 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)

Summary by Sourcery

Chores:

• Bump kubernetes from 31.0.0 to 32.0.0.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request bumps the kubernetes dependency from 31.0.0 to 32.0.0. The pyproject.toml and poetry.lock files were updated to reflect this change.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Updated the kubernetes dependency to version 32.0.0.	Updated the kubernetes dependency to '>=31,<33' in pyproject.toml.	pyproject.toml
Updated the poetry.lock file to reflect the new kubernetes dependency.	Updated the poetry.lock file with the new kubernetes dependency.	poetry.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud