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

job,controllers: clear history job must do in cluster, not in namespa… #561

Merged
merged 2 commits into from
Jul 1, 2022

Conversation

acekingke
Copy link
Contributor

…ce #559

What type of PR is this?

/bug

Which issue(s) this PR fixes?

Fixes #559

What this PR does?

Summary:

  1. according namespace and cluster name to reserve the job finished.

Special notes for your reviewer?

@acekingke acekingke self-assigned this Jun 29, 2022
@acekingke acekingke added the bug Something isn't working label Jun 29, 2022
@acekingke acekingke added this to the v2.2.0 milestone Jun 29, 2022
Copy link
Collaborator

@zhl003 zhl003 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@acekingke acekingke merged commit 5e05677 into radondb:main Jul 1, 2022
zhl003 pushed a commit to zhl003/radondb-mysql-kubernetes that referenced this pull request Aug 17, 2022
job,controllers: clear history job must do in cluster, not in namespa…
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 this pull request may close these issues.

【bug】a maximum of three jobs can be reserved in a mysql cluster
3 participants