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.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
kops reconcile
cluster command.Kubernetes 1.31 introduces stricter checks around the version-skew policy. While kOps has always followed the version-skew policy, there was an edge case: nodes that were added by an autoscaler during a rolling-update would not always follow the version-skew policy. We recommend trying the new
kops reconcile
command, see docs/tutorial/upgrading-kubernetes.md for more details.Other changes of note
Deprecations
Support for Kubernetes version 1.25 is deprecated and will be removed in kOps 1.31.
Support for Kubernetes version 1.26 is deprecated and will be removed in kOps 1.32.
Full Changelog: kubernetes/kops@v1.31.0-beta.1...v1.31.0
Changes since 1.31.0-beta.1
update cluster
does by @justinsb in Automated cherry pick of #17214: reconcile: if --yes is not provided, print the same output asupdate cluster
does kubernetes/kops#17223kops update
by @justinsb in Automated cherry pick of #17220: Remove reconcile flag fromkops update
kubernetes/kops#17226