Change explicit v1_28
feature to use latest
feature alias
#1292
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.
Simplify our build setup to always set our MAX as the latest version
k8s-openapi
exposes.This doesn't let us avoid all the automation to bump (still need an explicit version for k3d on CI for the minimum check), but it avoids having to bump all the readme and toml files for the latest dev-deps.
Brought up in #1291 (comment)
Have updated recommendations in https://kube.rs/kubernetes-version/ to more explicitly tell users to use
latest
unless they have a reason for it (before we where a bit vague about it - but now it's easier with the feature alias).