Bug 1378504

Summary: [RFE] Configuration option for max number of deploy attempts
Product: OpenShift Container Platform Reporter: Eric Rich <erich>
Component: RFEAssignee: Dan McPherson <dmcphers>
Status: CLOSED NOTABUG QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: aos-bugs, erich, jokerman, mkargaki, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-22 18:50:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.