Repository navigation
Conversation
dossett
requested review from
henry3260,
hussein-awala,
jedcunningham,
jscheffl and
shahar1
as code owners
November 16, 2026 15:30
Contributor
|
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-leaseAutomated nudge — ignore if you're not ready to rebase. This comment is updated in place on future |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(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
kubernetesclient 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.Generated-by: Codex (GPT-6) following the contribution guidelines