🌱 Sync release-1.10.7 with upstream release branch - #14
Merged
Merged
Conversation
faiq
requested changes
Dec 1, 2025
faiq
left a comment
faiq
left a comment
There was a problem hiding this comment.
this release 1.10.7 branch was created so we could avoid the cert manager bump. can you take the required changes from the upstream 1.10 branch and cherry pick them to here
…pick-13075-to-release-1.10 [release-1.10] 🌱 Add httpClientCache to runtime client
jimmidyson
force-pushed
the
jimmi/sync-upstream-release-1.10
branch
from
December 1, 2025 16:11
7219414 to
a4be13c
Compare
Member
Author
|
@faiq Pulled in just the single required change. |
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
3 participants
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.
What this PR does / why we need it:
Pulls in refactoring of the HTTP client used in ExtensionConfig reconciliation to use a cache rather than a new client every time for better scalability.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #