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

[bug]The cluster is deleted, but the automatic backup job is not deleted #570

Closed
qianfen2021 opened this issue Jul 4, 2022 · 1 comment · Fixed by #581
Closed

[bug]The cluster is deleted, but the automatic backup job is not deleted #570

qianfen2021 opened this issue Jul 4, 2022 · 1 comment · Fixed by #581
Assignees
Labels
bug Something isn't working
Milestone

Comments

@qianfen2021
Copy link

Describe the problem

The cluster is deleted, but the automatic backup job is not deleted
image
image

To Reproduce

1.Create a cluster and create a scheduled backup
2.Delete the cluster

Expected behavior

Environment:
the automatic backup job is deleted

  • RadonDB MySQL version:
@qianfen2021 qianfen2021 added the bug Something isn't working label Jul 4, 2022
@acekingke
Copy link
Contributor

delete cluster to delete the backup cr , it will use finalizer, do it next version.

acekingke added a commit to acekingke/radondb-mysql-kubernetes that referenced this issue Jul 5, 2022
acekingke added a commit that referenced this issue Jul 14, 2022
controller: delete cluster then delete backup cr #570
zhl003 pushed a commit to zhl003/radondb-mysql-kubernetes that referenced this issue Jul 18, 2022
zhl003 pushed a commit to zhl003/radondb-mysql-kubernetes that referenced this issue Aug 17, 2022
zhl003 pushed a commit to zhl003/radondb-mysql-kubernetes that referenced this issue Aug 17, 2022
controller: delete cluster then delete backup cr radondb#570
@qianfen2021 qianfen2021 added this to the v2.2.1 milestone Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants