Skip to content

📖 Chained and efficient upgrades for Clusters with managed topologies #12199

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

Jump to bottom
Merged
merged 10 commits into from
Aug 29, 2025
Merged

📖 Chained and efficient upgrades for Clusters with managed topologies #12199

merged 10 commits into from
Aug 29, 2025

Conversation

fabriziopandini
Copy link
Member

What this PR does / why we need it:

This proposal will allow Cluster API users with Clusters using managed topologies to upgrade by more than one minor
Kubernetes version by performing chained and efficient upgrades.

Which issue(s) this PR fixes *:
Fixes ##8616

/area clusterclass

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. area/clusterclass Issues or PRs related to clusterclass cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels May 13, 2025
@k8s-ci-robot k8s-ci-robot requested review from elmiko and sivchari May 13, 2025 12:45
@k8s-ci-robot k8s-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label May 13, 2025
sbueringer
sbueringer reviewed May 13, 2025
View reviewed changes
chrischdi
chrischdi reviewed May 13, 2025
View reviewed changes
sbueringer
sbueringer reviewed May 14, 2025
View reviewed changes
@sbueringer
Copy link
Member

Fine so far from my side

@fabriziopandini fabriziopandini changed the title [WIP] 📖 Chained and efficient upgrades for Clusters with managed topologies 📖 Chained and efficient upgrades for Clusters with managed topologies May 14, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 14, 2025
@fabriziopandini fabriziopandini mentioned this pull request May 22, 2025
Open
@fabriziopandini
Copy link
Member Author

Considering that most likely this change is not going to make this release, I added a commit reverting changes to users facing docs (we can re-apply them as soon as the proposal is implemented)

@fabriziopandini fabriziopandini added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 24, 2025
@sbueringer sbueringer mentioned this pull request Jun 25, 2025
Closed
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 17, 2025
@fabriziopandini fabriziopandini force-pushed the chained-upgrades-proposal branch from 82a8a62 to d1caee8 Compare August 25, 2025 16:07
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 25, 2025
@fabriziopandini
Copy link
Member Author

Rebased, fixed a few nits

sbueringer
sbueringer reviewed Aug 27, 2025
View reviewed changes
@fabriziopandini fabriziopandini force-pushed the chained-upgrades-proposal branch from b1cb976 to 6bb0b1b Compare August 27, 2025 16:50
@sbueringer
Copy link
Member

/lgtm
/approve

/hold
up to you

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 27, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 27, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: fb91f426747a117d8012e598318b30e15daa6940

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2025
@sbueringer
Copy link
Member

Discussed in the office hours today. Lazy consensus until Friday

@fabriziopandini
Copy link
Member Author

As per yesterday office's hour discussion, we are setting a lazy consensus deadline Friday 29th Aug

@sbueringer
Copy link
Member

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 29, 2025
@k8s-ci-robot k8s-ci-robot merged commit 79a5e28 into kubernetes-sigs:main Aug 29, 2025
17 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.12 milestone Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@chrischdi chrischdi chrischdi left review comments

@sbueringer sbueringer sbueringer left review comments

@elmiko elmiko Awaiting requested review from elmiko

@sivchari sivchari Awaiting requested review from sivchari

Assignees

@sbueringer sbueringer

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/clusterclass Issues or PRs related to clusterclass cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Milestone
v1.12
Development

Successfully merging this pull request may close these issues.
4 participants
@fabriziopandini @sbueringer @k8s-ci-robot @chrischdi