Sourced from kubernetes's releases.

Kubernetes Python Client v34.1.0 Stable Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v34.1.0.zip
cd client-python-v34.1.0
python setup.py install

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

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

Kubernetes Python Client v34.1.0 Beta 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v34.1.0b1.zip
cd client-python-v34.1.0b1
python setup.py install

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

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

Kubernetes Python Client v34.1.0 Alpha 1 Release

Getting started:

pip install --pre --upgrade kubernetes

Or from source, download attached zip file, then

unzip client-python-v34.1.0a1.zip
cd client-python-v34.1.0a1
</tr></table> 

... (truncated)

Sourced from kubernetes's changelog.

v34.1.0b1

Kubernetes API Version: v1.34.1

v34.1.0a1

Kubernetes API Version: v1.34.1

API Change

• Added omitempty and opt tag to the API v1beta2 AdminAccess type in the DeviceRequestAllocationResult struct. (kubernetes/kubernetes#132338, @​PatrickLaabs)

• Added a runtime.ApplyConfiguration interface implemented by all generated apply configuration types. (kubernetes/kubernetes#132194, @​alvaroaleman) [SIG API Machinery and Instrumentation]

• Added a detailed event for in-place pod vertical scaling completed, improving cluster management and debugging. (kubernetes/kubernetes#130387, @​shiya0705) [SIG API Machinery, Apps, Autoscaling, Node, Scheduling and Testing]

• Added a mechanism for configurable container restarts: container-level restart rules. This was an alpha feature behind the ContainerRestartRules feature gate. (kubernetes/kubernetes#132642, @​yuanwang04) [SIG API Machinery, Apps, Node and Testing]

• Added a new FileKeyRef field to containers, allowing them to load variables from files by setting this field.

  Introduced the EnvFiles feature gate to govern activation of this functionality. (kubernetes/kubernetes#132626, @​HirazawaUi) [SIG API Machinery, Apps, Node and Testing]

• Added driver-owned fields in ResourceSlice to mark whether the device was shareable among multiple resource claims (or requests) and to specify how each capacity could be shared between different requests.

  • Added user-owned fields in ResourceClaim to specify resource requirements against each device capacity.
  • Added scheduler-owned field in ResourceClaim.Status to specify how much device capacity is reserved for a specific request.
  • Added an additional identifier to ResourceClaim.Status for the device supports multiple allocations.
  • Added a new constraint type to enforce uniqueness of specified attributes across all allocated devices. (kubernetes/kubernetes#132522, @​sunya-ch) [SIG API Machinery, Apps, Architecture, CLI, Cluster Lifecycle, Network, Node, Release, Scheduling and Testing]

• Added new optional APIs in ResouceSlice.Basic and ResourceClaim.Status.AllocatedDeviceStatus. (kubernetes/kubernetes#130160, @​KobayashiD27) [SIG API Machinery, Apps, Architecture, Node, Release, Scheduling and Testing]

• Added support for specifying controlplane or cluster egress selectors in JWT authenticators via the issuer.egressSelectorType field in the AuthenticationConfiguration.jwt array. If unset, the previous behavior of using no egress selector is preserved. This functionality requires the StructuredAuthenticationConfigurationEgressSelector beta feature gate (enabled by default). (kubernetes/kubernetes#132768, @​enj) [SIG API Machinery, Auth and Testing]

• Added support in the Kubelet for monitoring the health of devices allocated via Dynamic Resource Allocation (DRA) and report it in the pod.status.containerStatuses.allocatedResourcesStatus field. This required the DRA plugin to implement the new v1alpha1 NodeHealth gRPC service. This feature was controlled by the ResourceHealthStatus feature gate. (kubernetes/kubernetes#130606, @​Jpsassine) [SIG Apps, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Etcd, Network, Node, Release, Scheduling, Storage and Testing]

• Added support in the kubelet's image pull credential tracking for service account-based verification. When an image was pulled using service account credentials via external credential providers, subsequent Pods using the same service account (UID, name, and namespace) could access the cached image without re-authentication for the lifetime of that service account. (kubernetes/kubernetes#132771, @​aramase) [SIG Auth, Node and Testing]

• Added validation to reject Pods using the PodLevelResources feature on Windows OS due to lack of support. The API server rejected Pods with pod-level resources and a Pod.spec.os.name targeting Windows. Kubelet on nodes running Windows also rejected Pods with pod-level resources at the admission phase. (kubernetes/kubernetes#133046, @​toVersus) [SIG Apps and Node]

• Added warnings when creating headless service with set loadBalancerIP,externalIPs and/or SessionAffinity. (kubernetes/kubernetes#132214, @​Peac36)

• Allowed pvc.spec.VolumeAttributesClassName to change from non-nil to nil. (kubernetes/kubernetes#132106, @​AndrewSirenko)

• Allowed setting the hostnameOverride field in PodSpec to specify any RFC 1123 DNS subdomain as the pod's hostname. The HostnameOverride feature gate was introduced to control enablement of this functionality. (kubernetes/kubernetes#132558, @​HirazawaUi) [SIG API Machinery, Apps, Network, Node and Testing]

• Changed underlying logic for Eviction Manager helper functions. (kubernetes/kubernetes#132277, @​KevinTMtz) [SIG Node, Scheduling and Testing]

• Changed underlying logic to propagate pod-level hugepage cgroup to containers when they did not specify hugepage resources.

  • Added validation to enforce the hugepage aggregated container limits to be smaller than or equal to pod-level limits. This was already enforced with the defaulted requests from the specified limits, however it did not make it clear about both hugepage requests and limits. (kubernetes/kubernetes#131089, @​KevinTMtz) [SIG Apps, Node and Testing]

• Corrected the documentation to clarify that podSelector is optional and described its default behavior. (kubernetes/kubernetes#131354, @​tomoish)

• DRA API: resource.k8s.io/v1alpha3 now only contains DeviceTaintRule. All other types got removed because they became obsolete when introducing the v1beta1 API in 1.32. before updating a cluster where resourceclaims, resourceclaimtemplates, deviceclasses, or resourceslices might have been stored using Kubernetes < 1.32, delete all of those resources before updating and recreate them as needed while running Kubernetes >= 1.32. (kubernetes/kubernetes#132000, @​pohly) [SIG Etcd, Node, Scheduling and Testing]

• DRA: Starting with Kubernetes 1.34, the alpha-level resource.k8s.io/admin-access label has been updated to resource.kubernetes.io/admin-access. Admins using the alpha feature and updating from 1.33 can set both labels, upgrade, then remove resource.k8s.io/admin-access when no downgrade is going to happen anymore. (kubernetes/kubernetes#131996, @​ritazh) [SIG Node and Testing]

• DRA: The scheduler plugin prevented abnormal filter runtimes by timing out after 10 seconds. This was configurable via the plugin configuration's FilterTimeout. Setting it to zero disabled the timeout and restored the behavior of Kubernetes <= 1.33. (kubernetes/kubernetes#132033, @​pohly) [SIG Node, Scheduling and Testing]

• DRA: When the prioritized list feature was used in a request and the resulting number of allocated devices exceeded the number of allowed devices per claim, the scheduler aborted the attempt to allocate devices early. Previously, it tried to many different combinations, which could take a long time. (kubernetes/kubernetes#130593, @​mortent) [SIG Apps, Node, Scheduling and Testing]

• DRA: removed support for the v1alpha4 kubelet gRPC API (added in 1.31, superseded in 1.32). DRA drivers using the helper package from Kubernetes >= 1.32 use the v1beta1 API and continue to be supported. (kubernetes/kubernetes#132574, @​pohly)

• Deprecated StreamingConnectionIdleTimeout field of the kubelet config. (kubernetes/kubernetes#131992, @​lalitc375)

• Dynamic Resource Allocation: Graduated core functionality to general availability (GA). This newly stable feature uses the structured parameters flavor of DRA. (kubernetes/kubernetes#132706, @​pohly) [SIG API Machinery, Apps, Auth, Autoscaling, Etcd, Node, Scheduling and Testing]

• Enabled kube-apiserver support for PodCertificateRequest and PodCertificate projected volumes (behind the PodCertificateRequest feature gate). (kubernetes/kubernetes#128010, @​ahmedtd) [SIG API Machinery, Apps, Auth, Cloud Provider, Etcd, Node, Storage and Testing]

• Extended resources backed by DRA feature allowed cluster operator to specify extendedResourceName in DeviceClass, and application operator to continue using extended resources in pod's requests to request for DRA devices matching the DeviceClass.

  NodeResourcesFit plugin scoring didn't work for extended resources backed by DRA. (kubernetes/kubernetes#130653, @​yliaog) [SIG API Machinery, Apps, Auth, Node, Scheduling and Testing]

• Extended the NodePorts scheduling plugin to consider hostPorts used by restartable init containers. (kubernetes/kubernetes#132040, @​avrittrohwer) [SIG Scheduling and Testing]

• Fixed a 1.33 regression that causes a nil panic in kube-scheduler when aggregating resource requested across container's spec and status. (kubernetes/kubernetes#132895, @​yue9944882) [SIG Node and Scheduling]

• Fixed prerelease lifecycle for PodCertificateRequest. (kubernetes/kubernetes#133350, @​carlory)

• Introduced OpenAPI format support for k8s-short-name and k8s-long-name in CustomResourceDefinition schemas. (kubernetes/kubernetes#132504, @​jpbetz) [SIG API Machinery, Architecture, Auth, CLI, Cloud Provider, Cluster Lifecycle, Instrumentation, Network, Node, Scheduling and Storage]

... (truncated)

• 5b23a44 Merge pull request #2455 from yliaog/automated-release-of-34.1.0-upstream-rel...
• 8866972 Updated the compatibility matrix and maintenance status
• 9bb2014 generated client change
• efa2b26 update changelog
• b374f2e update version constants for 34.1.0 release
• 9d14e9f Merge pull request #2452 from yliaog/automated-release-of-34.1.0b1-upstream-r...
• 749ec15 generated client change
• 14901c6 update changelog
• fe16bed update version constants for 34.1.0b1 release
• c66f45a Merge pull request #2448 from yliaog/automated-release-of-34.1.0a1-upstream-r...
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions