chore(deps): bump Kubernetes libraries to v0.36.3 (K8s 1.36.3) - #290
Merged
Conversation
Align the k8s.io stack to the latest 1.36 patch: k8s.io/api + client-go v0.36.2 -> v0.36.3, and the transitive apiextensions-apiserver / apiserver / component-base / kms v0.36.0 -> v0.36.3 (apimachinery was already v0.36.3). controller-runtime stays at v0.24.1 (latest, compatible with k8s.io v0.36). Within-minor patch bump: no source changes, generated manifests unchanged, full unit+envtest suite green (envtest against 1.36.2 — the newest 1.36.x envtest binary published upstream; no 1.36.3 envtest yet). Kind e2e stays on 1.35.x until upstream publishes a kindest/node:v1.36.x image. sgp4 and other pinned deps untouched.
thc1006
force-pushed
the
chore/k8s-1.36.3-upgrade
branch
from
July 31, 2026 01:30
be130e1 to
9ecd378
Compare
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
1 participant
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
Aligns the whole
k8s.iostack to K8s 1.36.3 (the latest 1.36 patch):k8s.io/apik8s.io/client-gok8s.io/apiextensions-apiserver(indirect)k8s.io/apiserver(indirect)k8s.io/component-base(indirect)k8s.io/kms(indirect)k8s.io/apimachinerysigs.k8s.io/controller-runtimeWhy it's low-risk
A within-minor patch bump (v0.36.2 → v0.36.3): no source changes,
controller-genregenerated the manifests with zero diff,go mod verifyclean, and the guarded deps (akhenakh/sgp4v1.0.1 — the deep-space propagation pin —coder/websocket, etc.) are untouched. controller-runtime v0.24.1 is already the latest release and is compatible with k8s.io v0.36.Verification
go build ./...+go vet ./...clean.make test(full unit + envtest suite) green — controller 90.5%, all packages pass.golangci-lint(v2.12.2) 0 issues.Upstream caveats (why this is "1.36.3 libs" not "1.36.3 everywhere")
ENVTEST_K8S_VERSIONis minor-pinned (1.36), so it auto-tracks the latest patch — no Makefile change.kindest/node:v1.36.ximage (only ≤v1.35.0 exists on Docker Hub), so the Kind-based e2e cluster cannot run 1.36 yet. This is an upstream limitation, not a config choice.