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 2023] Karmada namespace deletion protection mechanism #3728

Closed
XiShanYongYe-Chang opened this issue Jun 28, 2023 · 5 comments
Closed
Assignees

Comments

@XiShanYongYe-Chang
Copy link
Member

XiShanYongYe-Chang commented Jun 28, 2023

Description

On the Karmada control plane, the same namespace manages the namespaces of all member clusters in a unified manner. If a user performs a misoperation, the namespaces are deleted from the Karmada control plane, which means that the namespaces with the same names in all member clusters, including resources in the namespace, are deleted. For example, Deployment, Job, Configmap, and Secret. The impact will be catastrophic.

Therefore, we plan to provide a namespace deletion protection mechanism in Karmada. Users can add tags to the target namespace to prevent incorrect deletion. When deleting a namespace, users need to remove the tags before deleting the namespace.

Project extension: The same processing logic can be used to process Cluster objects and resource template objects.

Project link

https://summer-ospp.ac.cn/org/prodetail/235c40372?list=org&navpage=org

@XiShanYongYe-Chang
Copy link
Member Author

/assign @Vacant2333

@karmada-bot
Copy link
Collaborator

@XiShanYongYe-Chang: GitHub didn't allow me to assign the following users: Vacant2333.

Note that only karmada-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @Vacant2333

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Vacant2333
Copy link
Contributor

/assign @Vacant2333

@XiShanYongYe-Chang
Copy link
Member Author

All PRs have been merged in, thanks @Vacant2333
Now we can close it.
/close

@karmada-bot
Copy link
Collaborator

@XiShanYongYe-Chang: Closing this issue.

In response to this:

All PRs have been merged in, thanks @Vacant2333
Now we can close it.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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

No branches or pull requests

3 participants