-
Notifications
You must be signed in to change notification settings - Fork 710
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 sync PodGroup logic #1012
fix sync PodGroup logic #1012
Conversation
Are events regenerated again for terminated job during reconcile because of #965 ? |
@johnugeorge when we enable gang-scheduling in tf-operator, for every tfjob that is success or failure, in a single sync, the podgroup is created first and then get delete, and also regenerated two events. that is to say we need at least four api request that is useless and it increase the burden of api-server. |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Can you do the similar change to v1beta2?
@gaocegege Yes, done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[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 |
/test kubeflow-tf-operator-presubmit |
Thanks for your contribution! |
fix #1011
/assign @gaocegege @richardsliu
This change is