Bug 1378504 - [RFE] Configuration option for max number of deploy attempts
Summary: [RFE] Configuration option for max number of deploy attempts
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 15:02 UTC by Eric Rich
Modified: 2019-11-14 09:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-22 18:50:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eric Rich 2016-09-22 15:02:55 UTC 
Description of problem:

There should be a configuration for deployment, that defines the maximum number of deployment attempts (for some time period) to help avoid "CrashLoopBackOff" messages, and containers created as a result using a users quota.
Comment 1 Michail Kargakis 2016-09-22 15:15:25 UTC 
Why isn't TimeoutSeconds in dc.spec.strategy.*params not enough?
Comment 2 Michail Kargakis 2016-09-22 15:17:11 UTC 
What we probably want here is infant mortality so we can detect permanent errors and abort the deployment sooner than the specified timeout

https://github.com/kubernetes/kubernetes/issues/18568
Comment 3 Eric Rich 2016-09-22 18:50:49 UTC 
I think what we have in the docs: https://docs.openshift.org/latest/dev_guide/deployments.html#strategies

(In reply to Michail Kargakis from comment #1)

> Why isn't TimeoutSeconds in dc.spec.strategy.*params not enough?

Is enough to cover what this RFE is asking for.
Note You need to log in before you can comment on or make changes to this bug.