-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 MinReadySeconds in deployment configs #9852
Conversation
[test] |
#9888 [test] |
[test] |
@@ -297,6 +297,11 @@ type DeploymentConfigSpec struct { | |||
// Strategy describes how a deployment is executed. | |||
Strategy DeploymentStrategy | |||
|
|||
// Minimum number of seconds for which a newly created pod should be ready |
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.
Make this comment as MinReadSeconds is the minimum...
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.
ok
@Kargakis minor suggestions, but the code looks great! Can you also please add minReadySeconds into |
Comments addressed - @openshift/api-review can I get an approval for this? Last upstream feature and then DeploymentConfigs are a superset of Deployments. |
API approved |
LGTM |
Evaluated for origin test up to 1b0111d |
continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6382/) |
[merge] |
1 similar comment
[merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6409/) (Image: devenv-rhel7_4616) |
[merge] |
Evaluated for origin merge up to 1b0111d |
@mfojtik @ironcladlou @openshift/api-review
Fixes #7114
Part of https://trello.com/c/Mljldox7/643-8-deployments-downstream-support-for-upstream-features