Skip to content
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.

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

[Summer OSPP 2024] Karmada supports smooth rollback of a single cluster #5380

Open
1 of 7 tasks
chaosi-zju opened this issue Aug 15, 2024 · 1 comment
Open
1 of 7 tasks
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@chaosi-zju
Copy link
Member

chaosi-zju commented Aug 15, 2024

What would you like to be added:

Karmada supports joining a single cluster and promoting the existing resources from the original cluster. It also supports unjoining a single cluster and removing it from Karmada's control. When unjoining a single cluster, Karmada cleans up resources on the cluster that were previously controlled by Karmada, but in some removal scenarios, users want these resources to continue to remain in the single cluster.

Karmada hopes to attract more users to try to evolve from a single cluster to a multi-clusters. This ability can reduce the trial-and-error costs of users. When users want to fall back from multi-clusters to a single cluster, it can minimize the impact on the single cluster after rollback.

Therefore, we plan to provide a smooth rollback capability. When removing a managed cluster, users can choose to retain the resources in the original cluster.

Project link: https://summer-ospp.ac.cn/org/prodetail/245c40436

Parts of: #4879

Desired outcomes:

@chaosi-zju chaosi-zju added the kind/feature Categorizes issue or PR as related to a new feature. label Aug 15, 2024
@wulemao
Copy link
Contributor

wulemao commented Aug 16, 2024

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
Status: No status
Development

No branches or pull requests

2 participants