chore(deps): Update k8s-openapi and kube-* dependencies#433
Draft
sfleen wants to merge 1 commit intoolix0r:mainfrom
Draft
chore(deps): Update k8s-openapi and kube-* dependencies#433sfleen wants to merge 1 commit intoolix0r:mainfrom
sfleen wants to merge 1 commit intoolix0r:mainfrom
Conversation
This performs the following dependency updates: `k8s-openapi`: 0.25 -> 0.27 `kube`: 1.1 -> 3 `kube-client`: 1.1 -> 3 `kube-core`: 1.1 -> 3 `kube-runtime`: 1.1 -> 3 These dependencies are farily tightly coupled, so must be updated together in a batch. The most viral change in this PR is k8s-openapi trasitioning from `chrono` to `jiff` for timestamp/durations, other than that the changes have been relatively small.
sfleen
force-pushed
the
sfleen/kube-dep-update
branch
from
e1acbab to
c7a0426
Compare
cratelyn
reviewed
Jan 22, 2026
Collaborator
There was a problem hiding this comment.
cargo nextest run --workspace --exclude=kubert-examples --all-features
error: rustc 1.85.1 is not supported by the following packages:
kube@3.0.0 requires rustc 1.88.0
kube-client@3.0.0 requires rustc 1.88.0
kube-core@3.0.0 requires rustc 1.88.0
kube-runtime@3.0.0 requires rustc 1.88.0
Either upgrade rustc or select compatible dependency versions with
`cargo update <name>@<current-ver> --precise <compatible-ver>`
where `<compatible-ver>` is the latest version supporting rustc 1.85.1
the changes here look good to me. i see one outstanding issue here is that we have a failing job in CI because of minimum toolchain support.
it seems that we should either (a) consider removing that job, or (b) update the versions we run tests against in CI. my preference is for (b), since the current stable has now moved up to 1.93.
Comment on lines
+24
to
+27
| kube-client = { version = "3", default-features = false } | ||
| kube-core = { version = "3", default-features = false } | ||
| kube-runtime = { version = "3", default-features = false } | ||
| kube = { version = "3", default-features = false } |
Collaborator
There was a problem hiding this comment.
nit, not a blocker: can we put 3.0 here?
i find those are nice as a loose signal of when we upgraded to a particular major version, but i see there are other dependencies here specified solely by major version.
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
2 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.
This performs the following dependency updates:
k8s-openapi: 0.25 -> 0.27kube: 1.1 -> 3kube-client: 1.1 -> 3kube-core: 1.1 -> 3kube-runtime: 1.1 -> 3These dependencies are farily tightly coupled, so must be updated together in a batch.
The most viral change in this PR is k8s-openapi trasitioning from
chronotojifffor timestamp/durations, other than that the changes have been relatively small.