Skip to content

chore(deps): upgrade Kubernetes client to kube 5 - #5646

Merged
SDAChess merged 2 commits into
mainfrom
chore/2019-update-kube-client/SDAChess
Nov 18, 2026
Merged

SDAChess merged 2 commits into
mainfrom
chore/2019-update-kube-client/SDAChess

Conversation

@SDAChess

@SDAChess SDAChess commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

Summary

Upgrade the Kubernetes client stack from kube 0.99 / k8s-openapi 0.24 to kube 5.0.0 / k8s-openapi 0.29, selecting the Kubernetes 1.33 API schema. This also removes kube-client's deprecated serde_yaml dependency.

Related Issue

Closes #2019

Changes

  • Adapt boxed API errors, Jiff timestamps, and optional NetworkPolicy selectors to the new APIs.
  • Refresh affected Cargo lockfiles, keeping the kube family aligned at 5.0.0 and Jiff at 0.2.38.
  • Set the minimum tested Kubernetes version to 1.33 and pin the conformance baseline to K3s 1.33.13+k3s2 with a verified installer checksum.

Release Notes

Kubernetes 1.33 is the minimum tested version. Older cluster versions are untested; compatibility is not guaranteed.

Testing

  • Local checks appropriate to the affected code and behavior pass
  • Existing unit tests updated and passing
  • Kubernetes E2E validation through PR CI

Passed all-target compilation and Clippy with warnings denied for the Kubernetes compute driver, Kubernetes Secrets driver, and server. All 443 selected unit tests pass: 335 compute-driver, 18 Kubernetes Secrets, 17 peer-authentication, 19 certificate-generation, and 54 OIDC tests.

Formatting, tracked lockfile consistency/alignment, crypto-policy regression fixtures, and dependency license/ban/source checks pass. Fern validation and docs navigation pass; the K3s playbook YAML and installer checksum were verified. Validation used Rust 1.95; dependency resolution selected Rust 1.94-compatible versions.

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

@SDAChess SDAChess added test:e2e Requires end-to-end coverage dependencies Pull requests that update a dependency file test:e2e-kubernetes Requires Kubernetes end-to-end coverage labels Nov 17, 2026
@github-actions

Copy link
Copy Markdown

Label test:e2e applied for b0d7ab6. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute the standard E2E suite after building the required gateway, sandbox, and supervisor images once. The matching required CI gate status on this PR will flip green automatically once the run finishes.

@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 17, 2026
@github-actions

Copy link
Copy Markdown

Label test:e2e-kubernetes applied for b0d7ab6. Open the existing run and click Re-run all jobs to execute with the label set. The run will execute Kubernetes HA and credential-driver E2E after building the required gateway, sandbox, and supervisor images once. This is an optional proof-of-life suite; failures are visible in the workflow run but do not publish a required CI gate status.

@github-actions

Copy link
Copy Markdown

@SDAChess SDAChess added area:drivers Compute and secret drivers, host OS/architecture support, backend isolation, and lifecycle. topic:kubernetes Kubernetes operators, CRDs, deployment controllers, and native Kubernetes API integration. labels Nov 17, 2026
@SDAChess
SDAChess force-pushed the chore/2019-update-kube-client/SDAChess branch from b0d7ab6 to e2ca1cb Compare November 17, 2026 17:14
@github-actions

Copy link
Copy Markdown

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

1. helm — No explicit risk acceptance found

The Kubernetes deployment prerequisites change from supported Kubernetes 1.29+ to minimum-tested 1.33 with compatibility explicitly not guaranteed for older clusters.

  • Impact: Existing Helm deployments on Kubernetes 1.29–1.32 lose their documented compatibility guarantee during a patch upgrade, even though runtime failure on those clusters is not established.
  • Action: Preserve Kubernetes 1.29–1.32 compatibility and its documented guarantee in v0.1.9; defer any support withdrawal to a minor release with notice and actionable cluster-upgrade guidance.
  • PR: chore(deps): upgrade Kubernetes client to kube 5 #5646
Review details
  • Execution: complete
  • Candidate: PR #5646 (20693a83f1b2603cf4dcfd185f0a4d52b902a131)
  • Baseline: 624aceea32934f73c350ede3f2185880816a030c (624aceea32934f73c350ede3f2185880816a030c)
  • Reviewed: rust-sdk, python-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run

alangou
alangou previously approved these changes Nov 17, 2026
@SDAChess
SDAChess enabled auto-merge November 17, 2026 17:21
@SDAChess
SDAChess added this pull request to the merge queue Nov 17, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 17, 2026
Signed-off-by: Simon Scatton <sscatton@nvidia.com>
Signed-off-by: Simon Scatton <sscatton@nvidia.com>
@SDAChess
SDAChess force-pushed the chore/2019-update-kube-client/SDAChess branch from e2ca1cb to b987d52 Compare November 18, 2026 13:41
@SDAChess SDAChess added area:build CI/CD workflows, releases, build targets, packaging, and artifact publication. and removed area:drivers Compute and secret drivers, host OS/architecture support, backend isolation, and lifecycle. labels Nov 18, 2026
@SDAChess
SDAChess merged commit 9ec37d2 into main Nov 18, 2026
267 of 274 checks passed
@SDAChess
SDAChess deleted the chore/2019-update-kube-client/SDAChess branch November 18, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:build CI/CD workflows, releases, build targets, packaging, and artifact publication. dependencies Pull requests that update a dependency file state:accepted A maintainer decided OpenShell should pursue this issue test:e2e Requires end-to-end coverage test:e2e-kubernetes Requires Kubernetes end-to-end coverage topic:kubernetes Kubernetes operators, CRDs, deployment controllers, and native Kubernetes API integration.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(deps): update kube client dependencies

2 participants