Bug 1397634

Summary: Vague information on Rolling Strategy
Product: OpenShift Container Platform Reporter: brice <bfallonf>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED WONTFIX QA Contact: Vikram Goyal <vigoyal>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.2.0CC: aos-bugs, gnelson, jokerman, 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: 2018-04-26 13:18:24 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 brice 2016-11-23 03:07:45 UTC 
As per: https://docs.openshift.com/container-platform/3.3/dev_guide/deployments/deployment_strategies.html#when-to-use-a-rolling-deployment

The "steps" under "The Rolling strategy will:" are vague.

1. "Execute any pre lifecycle hook" Should probably be "hooks"

2. "Surge count" is not clear. Does that work with the "maxsurge" part of the example above?

3. "Scale down the old replication controller based on the max unavailable count." Does this mean based on the 10% from the example above? How does this work?
Comment 1 Gaurav Nelson 2018-04-26 13:18:24 UTC 
The latest version docs differ, closing this one.