-
Notifications
You must be signed in to change notification settings - Fork 1.4k
fix: webhook fail to add lifecycle to Spark3 executor pods #2458
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: webhook fail to add lifecycle to Spark3 executor pods #2458
Conversation
Before this fix if you have a Spark 3.x spec where the executor has a lifecycle then the webhook will fail to identify the correct container. As described in issue [2457](kubeflow#2457) Signed-off-by: pvbouwel <[email protected]>
Signed-off-by: pvbouwel <[email protected]>
@pvbouwel Thank you for reporting the bug and raising a PR to fix it! |
Signed-off-by: pvbouwel <[email protected]>
Pushed formatting. Thanks for the info; I will look into the pod template feature such that we can migrate our workflows early on |
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ChenYi015 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 |
* bugfix: A lifecycle on a spark3 executor should not fail Before this fix if you have a Spark 3.x spec where the executor has a lifecycle then the webhook will fail to identify the correct container. As described in issue [2457](#2457) Signed-off-by: pvbouwel <[email protected]> * tests: Add coverage for spark3 executor with a lifecycle Signed-off-by: pvbouwel <[email protected]> * make go-fmt Signed-off-by: pvbouwel <[email protected]> --------- Signed-off-by: pvbouwel <[email protected]> (cherry picked from commit 3128c7f)
Before this fix if you have a Spark 3.x spec where the executor has a lifecycle then the webhook will fail to identify the correct container. As described in issue 2457
Purpose of this PR
Solve the bug as detailed in #2457 where spark3 executors are blocked if they have a lifecycle
Proposed changes:
Change Category
Rationale
Checklist
Additional Notes