-
Notifications
You must be signed in to change notification settings - Fork 40.3k
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
add podReplacementPolicy and terminating field to job api #119301
add podReplacementPolicy and terminating field to job api #119301
Conversation
/sig apps |
/assign @deads2k @alculquicondor @mimowo To make the API review limited to scope I moved the api changes in #117015 to here. |
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.
validation.go and strategy.go should be part of this PR, as it is part of the api-review.
/label api-review |
b824acc
to
4024063
Compare
Ah! I pushed up those changes. |
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
Template: validPodTemplateSpecForGeneratedRestartPolicyNever, | ||
Selector: validGeneratedSelector, | ||
Template: validPodTemplateSpecForGeneratedRestartPolicyNever, | ||
PodReplacementPolicy: &failedPodReplacement, |
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.
leave this one nil (so we test that nil passes validation)
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.
Sorry, I find this a bit confusing..
Do you mean leave it as:
PodReplacementPolicy: nil
or
Just drop the field entirely?
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.
they are equivalent and I prefer just dropping the field.
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.
Ah I see. Pushed up the last of my changes.
LGTM label has been added. Git tree hash: 4e1e7cb8c7d6edef6063caec9f8dc2a00812c239
|
4024063
to
800ecc3
Compare
/lgtm |
LGTM label has been added. Git tree hash: f87435739cef55272204dc6dcfdb4b0335e141b6
|
Implementation is approved |
/retest |
1 similar comment
/retest |
/skip |
exception request received. |
Exception was approved and release team gave me the goahead to cancel the hold. https://groups.google.com/g/kubernetes-sig-release/c/8m9_MloKhoI /hold cancel |
@Atharva-Shinde can you help with adding back the 1.28 milestone? |
/milestone v1.28 |
b625dbc
to
ce92952
Compare
/test pull-kubernetes-e2e-gce |
@kannon92: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/lgtm |
LGTM label has been added. Git tree hash: a359ea62be68ecadf2dd4722411ae965f990855a
|
/triage accepted |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Add API changes for https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/3939-allow-replacement-when-fully-terminated.
Which issue(s) this PR fixes:
Partial Resolve kubernetes/enhancements#3939
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: