Repository navigation
chore(deps): upgrade Kubernetes client to kube 5 - #5646
Conversation
|
Label |
|
Label |
|
🌿 Preview your docs: https://nvidia-preview-pr-5646.docs.buildwithfern.com/openshell |
b0d7ab6 to
e2ca1cb
Compare
Compatibility review (advisory)New or updated breaking changes; see the full report for all findings. 1. helm — No explicit risk acceptance foundThe Kubernetes deployment prerequisites change from supported Kubernetes 1.29+ to minimum-tested 1.33 with compatibility explicitly not guaranteed for older clusters.
Review details
Advisory review; publication gates are unchanged. |
Signed-off-by: Simon Scatton <sscatton@nvidia.com>
Signed-off-by: Simon Scatton <sscatton@nvidia.com>
e2ca1cb to
b987d52
Compare
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
Release Notes
Kubernetes 1.33 is the minimum tested version. Older cluster versions are untested; compatibility is not guaranteed.
Testing
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