Skip to content

Upgrade kubernetes client to version 37 - #77168

Open
dossett wants to merge 3 commits into
apache:mainfrom
dossett:upgrade-kubernetes-client-37
Open

dossett wants to merge 3 commits into
apache:mainfrom
dossett:upgrade-kubernetes-client-37

Conversation

@dossett

@dossett dossett commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

(Upgrading the cncf/kubernetes provider is a breaking change for that provider and would required a major release of the provider.)

The code for this PR was written by Codex, but this PR description was written by a human.

The kubernetes client took a leap forward with version 37, upgrading the version of the openapi library used to generate it. The upgraded version of the generator contains a fix related to how often it was needlessly setting the python logging level. Every time the level was set it cleared the caches of all in-process loggers. This doesn't sound like a lot, but at scale the work to lazily repopulate them will really add up.

Check out this benchmark. Instantiating a pod with PodGenerator with the current provider sets the log level (and clears all logging caches) 132 times. With this PR that happens zero times.

The other changes in this PR are to account for the public changes in kubernetes. Update timeout handling, empty-template deserialization, examples, and dependency metadata for the new client while preserving pod-template behavior. Document migration requirements for keyword-only constructors and stricter validation.


  • Generative AI used: Codex (GPT-6)

Generated-by: Codex (GPT-6) following the contribution guidelines

@boring-cyborg boring-cyborg Bot added area:DAG-processing area:providers kind:documentation provider:cncf-kubernetes Kubernetes (k8s) provider related issues provider:google Google (including GCP) related issues labels Nov 16, 2026
@dossett dossett changed the title Upgrade kubernetes client 37 Upgrade kubernetes client to version 37 Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

uv.lock on main just moved via #77150 ("Upgrade datasets to 5.2.0 and restore compatible filesystem dependencies for HF provider"), commit 0289ce3 and this PR currently conflicts.

Quickest fix:

git fetch upstream main && git rebase upstream/main
rm uv.lock && uv lock
git add uv.lock && git rebase --continue
git push --force-with-lease

Automated nudge — ignore if you're not ready to rebase. This comment is updated in place on future uv.lock bumps.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant