Bug 1397634 - Vague information on Rolling Strategy
Summary: Vague information on Rolling Strategy
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 03:07 UTC by brice
Modified: 2018-04-26 13:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-26 13:18:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.