Kubernetes Python Client v36.0.1 Stable Release

   |   3 minute read   |   Using 483 words

The kubernetes-client/python project published the v36.0.1 stable tag on May 20, 2026. This is a patch release in the 36.0.x line, marked as non prerelease, so it is intended for production installs rather than testing.

The full release notes and downloads are on the GitHub release page. The release notes themselves are intentionally short. The actual per commit list of changes lives in the CHANGELOG.md file on the release-36.0 branch in the repository.

What this release is

v36.0.1 is the first patch on top of the 36.0 series. The official Python client tracks Kubernetes API server versions, so the 36.x line corresponds to the matching Kubernetes server major. A point release on a stable line is almost always a fix release: bug fixes in generated models, packaging tweaks, or doc updates. The release does not call out breaking changes in its notes, and the prerelease flag is false, so existing 36.0.0 users can plan a straight upgrade.

For the exact commit list, the project points at the in repo changelog on the release branch rather than duplicating it on the GitHub release page.

How to install

The release page ships two install paths.

From PyPI, using the upstream snippet:

pip install --pre --upgrade kubernetes

For a strict pin to this exact release:

pip install "kubernetes==36.0.1"

From the attached source zip:

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

The zip is attached to the release on GitHub. Most teams will not need it. PyPI is the canonical channel and is what CI pipelines should use.

Examples and changelog

The project keeps a per branch examples directory. For the 36.0 line the examples live under release-36.0/examples in the repo. They cover the patterns most users hit first: in cluster config, loading a kubeconfig, watch streams, exec into pods, log streaming, and the dynamic client for unknown resource kinds.

For the exact diff between v36.0.0 and v36.0.1, read CHANGELOG.md on the release-36.0 branch. That file is the source of truth for this release.

Upgrade notes

Nothing in the release notes flags a breaking change. For users on v36.0.0 the upgrade is a plain pip bump. Things worth checking after the bump:

  • The pinned version in requirements.txt, pyproject.toml, or constraints.txt
  • Any code that imports directly from kubernetes.client.models, since model classes are generated and can shift between patches
  • Anything that depended on the exact shape of API responses, since the generated client tracks the OpenAPI spec from the matching server version
  • Container image base layers if you ship the client inside a sidecar or operator image

Users still on older majors should treat the move to 36.x as a separate upgrade. The official client follows the Kubernetes one minor version skew policy in spirit, so jumping across several majors at once is more likely to surface deprecated API removals on the server than on the client.

Where to get it



denis256 at denis256.dev