Skip to content

docs: update 1.32 release note with beta release #17254

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 8, 2025
Merged

docs: update 1.32 release note with beta release #17254

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/releases/1.32-NOTES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,17 @@

This is a document to gather the release notes prior to the release.

kOps 1.32 is planned as a small release without significant additional features beyond updated support for kubernetes 1.32 and associated ecosystem updates. Significant kOps features will instead target kOps 1.33.

# Significant changes

## Kubernetes minor version upgrades to 1.31 or later should be performed using the `kops reconcile cluster command.

* Kubernetes 1.31 introduced 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](https://github.com/kubernetes/kops/blob/master/docs/tutorial/upgrading-kubernetes.md) for more details.
The `kops reconcile` functionality was introduced in kOps 1.32.

* TODO

## Some Feature
Expand Down
Loading