-
Notifications
You must be signed in to change notification settings - Fork 699
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
fix the bug of keeping creating new pdb #539
Conversation
Thanks for your contribution! @k82cn Do we support owner reference based gang scheduling in kube-arbitrator? If that we could eliminate the hack about PDB. |
/ok-to-test Please fix the error in Travis CI. |
I think it's ok now. |
I do not think so. It seems that the Travis reported that the import order is not followed. Our checker is weird and it returns some errors which is not caused by your code. Let us see if it works well 😄 |
I looked through the code in kube-arbitrator. It seems that the feature /cc @mitake Would you please take a look? |
|
It seems that mitake is not around. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gaocegege 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 |
@gaocegege sorry for being late, this PR looks good to me. |
@mitake haha No worry I just want to double check it. |
Really thanks for your help ! |
* fix the bug of keeping creating new pdb * fix the error in Travis CI
* fix the bug of keeping creating new pdb * fix the error in Travis CI
The original code will let the controller keep creating new pdb for the job since the names are not the same.
They only have the same prefix which is GenerateName: "tf-job-pdb-".
I try to fix it by assigning the name, "tf-job-pdb-" + j.job.ObjectMeta.Name, to the pdb in order to make controller only create pdb once.
This change is