Skip to content

chore(aws-eks-cluster): correct v9.0.0 breaking-change notes to the shipped zero-drain behavior - #920

Merged
alexlokshin-czi merged 2 commits into
mainfrom
alokshin/v9-changelog-zero-drain
Aug 27, 2026
Merged

alexlokshin-czi merged 2 commits into
mainfrom
alokshin/v9-changelog-zero-drain

Conversation

@alexlokshin-czi

Copy link
Copy Markdown
Contributor

Summary

The v9.0.0 changelog's BREAKING CHANGES entry describes the drain-based design from the first commit on #914 (release-please took that commit's footer), but the shipped code is the zero-drain revision: the legacy hash-named pool is kept and neutered in place (limits.cpu=0), no node drains at upgrade, and karpenter_legacy_nodepool = false removes the pool once empty. This rewrites the entry to match the code — validated in the nonprod soak (dev-cilium-test upgraded with 0 to destroy; its legacy pool emptied via consolidation within 2 days).

Docs-only; chore: so release-please cuts nothing.

🤖 Generated with Claude Code

…hipped zero-drain behavior

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@alexlokshin-czi
alexlokshin-czi merged commit d3aaf85 into main Aug 27, 2026
10 checks passed
@alexlokshin-czi
alexlokshin-czi deleted the alokshin/v9-changelog-zero-drain branch August 27, 2026 16:18
@czi-github-helper czi-github-helper Bot mentioned this pull request Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants