Upgrade to Kubernetes SDK to support 1.35#1168
Merged
Conversation
LukeButters
approved these changes
Nov 23, 2025
APErebus
force-pushed
the
ap/upgrade-k8s-sdk
branch
from
c390c9a to
54ada1b
Compare
4 tasks
APErebus
changed the title
APErebus
changed the title
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.
Background
v18 of the Kubernetes SDK (which supports K8s 1.34) was released 2 months ago, so it's time to upgradev19 of the Kubernetes SDK (which supports K8s 1.35) was released ~2 weeks ago, but we failed to upgrade to v18 which supported 1.34. Expediting this upgrade due to that lag
Results
18.0.5BouncyCastle.Cryptographywas required to be upgraded to2.6.2(as a transient dependency)How to review this PR
Quality ✔️
Pre-requisites