-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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: Apply podSpecPatch in woc.execWf.Spec
and template to pod sequentially
#12476
Conversation
I haven't looked at it in detail, but a quick observation that it does look like a different approach from #11222 (not necessarily good or bad) Also DCO check is still failing as it's expecting a different/real email address |
Ah so this allows overriding with |
There is a new bug in the original logic here: see #12729 (comment) and it is also fixed in this PR. |
null
after merge(wf/tmpl).Fixes #…woc.execWf.Spec
and template to pod sequentially
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.
looks good
…tially. Fixes argoproj#11130 argoproj#13122 Signed-off-by: oninowang <oninowang@tencent.com>
Hi @terrytangyuan , could you have a look at this PR again |
Fixes #11130
Fixes #13122
Motivation
podSpecPatch
missed keywordsnull
after merging(wf/tmpl), so removing fields in map/slice bypodSpecPatch
does not work.podSpecPatch
does not work when workflow is submitted from template byworkflowTemplateRef
.Modifications
podSpecPatch
to the pod spec sequentially avoiding the merge operation.podSpecPatch
inwoc.execWf.Spec
instead ofwoc.wf
.Verification
UT and local test