Bump kubernetes from 35.0.0 to 36.0.2

[dependabot]

Bumps kubernetes from 35.0.0 to 36.0.2.

Release notes

Sourced from kubernetes's releases.

Kubernetes Python Client v36.0.2 Stable Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v36.0.2.zip
cd client-python-v36.0.2
python setup-release.py install

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

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

Kubernetes Python Client v36.0.1 Stable Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v36.0.1.zip
cd client-python-v36.0.1
python setup-release.py install

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

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

Kubernetes Python Client v36.0.0 Beta 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v36.0.0b1.zip
cd client-python-v36.0.0b1
</tr></table> 

... (truncated)

Changelog

Sourced from kubernetes's changelog.

v36.0.2

Kubernetes API Version: v1.36.1

Uncategorized

• Restored backward compatibility for Configuration.auth_settings(): the legacy api_key['authorization'] lookup is honored as a fallback when api_key['BearerToken'] is not set, fixing 401 Unauthorized regressions seen after upgrading to v36.0.0 (#2595). (#2604, @​GK-07)

v36.0.1

Kubernetes API Version: v1.36.1

Bug or Regression

• Fix load_incluster_config() and load_kube_config() (sync and async, with a static token) so requests carry an Authorization header on kubernetes-client/python v36+. Without this fix, in-cluster pods upgrading to v36 silently send unauthenticated requests and the apiserver rejects them as system:anonymous. (#2585, @​Jmacek)

Deprecation

• Support new exec v5 websocket subprotocol (#2486, @​aojea)

v36.0.0

Kubernetes API Version: v1.36.1

v36.0.0b1

Kubernetes API Version: v1.36.1

Deprecation

• Support new exec v5 websocket subprotocol (#2486, @​aojea)

v36.0.0a3

Kubernetes API Version: v1.36.0

v36.0.0a2

Kubernetes API Version: v1.36.0

v36.0.0a1

Kubernetes API Version: v1.36.0

API Change

• ACTION REQUIRED: DRA (Dynamic Resource Allocation) drivers and controllers now require granular RBAC permissions to update ResourceClaim statuses when the DRAResourceClaimGranularStatusAuthorization feature gate is enabled (beta in v1.36). Schedulers and controllers must be granted update/patch on resourceclaims/binding. DRA drivers must be granted associated-node:update or arbitrary-node:update (or patch equivalents) on resourceclaims/driver, restricted by their specific resourceNames. (kubernetes/kubernetes#134947, @​aojea) [SIG API Machinery, Apps, Auth, Instrumentation, Node, Scheduling and Testing]
• ACTION REQUIRED: Removed the integrated support for flex-volumes in kubeadm. Users were advised to migrate away from flex-volumes as recommended by SIG Storage since v1.22. If kubeadm users wish to continue using the feature, they need a custom image for the KCM that is not based on distroless, pass the KCM flag --flex-volume-plugin-dir, and mount the directory /usr/libexec/kubernetes/kubelet-plugins/volume/exec in the KCM static pod using kubeadm's extraVolumes mechanism before upgrading to v1.36. Previously, kubeadm automatically did the mounting if the user passed the flag. (kubernetes/kubernetes#136423, @​neolit123) [SIG Cluster Lifecycle]
• ACTION REQUIRED: Renamed metric etcd_bookmark_counts to etcd_bookmark_total. If you are using custom monitoring dashboards or alerting rules based on the etcd_bookmark_counts metric, update them to use the new etcd_bookmark_total metric. (kubernetes/kubernetes#136483, @​petern48) [SIG API Machinery, Etcd, Instrumentation and Testing]
• Added SchedulingConstraints to express topology-aware scheduling (TAS) constraints for PodGroup scheduling behind the TopologyAwareWorkloadScheduling feature gate. Added the TopologyPlacement plugin implementing the PlacementGenerate extension point to take constraints into consideration during PodGroup scheduling. (kubernetes/kubernetes#137271, @​brejman) [SIG API Machinery, Apps, Auth, CLI, Cloud Provider, Etcd, Node, Scheduling and Testing]

... (truncated)

Commits

• 1f2df03 Merge pull request #2607 from yliaog/automated-release-of-36.0.2-upstream-rel...
• 348f673 Merge pull request #2605 from yliaog/release-36.0
• 70e680e Apply hotfix for commit: 5621a4c2cf5cc278e8f45ce759ce44c057f1dbe2
• 9683d06 generated client change
• d2cb000 update version constants for 36.0.2 release
• 17cf4e1 update changelog with release notes from master branch
• 8be4ce3 added breaking change on V1ServiceSpec fields cluster_i_ps and external_i_ps ...
• a05fe9e Merge pull request #2599 from yliaog/automated-release-of-36.0.1-upstream-rel...
• 33827fa updated compatibility matrix and maintenance status
• 8836c4c generated client change
• 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 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)