ROX-34999: add documentation for central.rolloutStrategy - #118387
ROX-34999: add documentation for central.rolloutStrategy#118387johannes94 wants to merge 1 commit into
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@johannes94: This pull request references ROX-34999 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
size/XS
|
🤖 Wed Aug 19 13:25:08 - Prow CI generated the docs preview: |
|
@johannes94: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| |Use this parameter to specify the image pull secrets for the Central image. | ||
|
|
||
| |`central.rolloutStrategy` | ||
| | Specifies the deployment rollout strategy for Central. Set to `RollingUpdate` to reduce downtime during upgrades and restarts. |
|
|
||
| |`central.rolloutStrategy` | ||
| | Specifies the deployment rollout strategy for Central. Set to `RollingUpdate` to reduce downtime during upgrades and restarts. | ||
| The default value is `Recreate`. A RollingUpdate will start a new central Pod, while the old keeps running until the new Pod is ready. |
There was a problem hiding this comment.
changes:
A RollingUpdate value will start a new Central pod and keep the old pod running until the new pod is ready.
There was a problem hiding this comment.
Oops, forgot that the backtick charaters would be interpreted. Surround RollingUpdate with backtick (`) characters.
| |`central.rolloutStrategy` | ||
| | Specifies the deployment rollout strategy for Central. Set to `RollingUpdate` to reduce downtime during upgrades and restarts. | ||
| The default value is `Recreate`. A RollingUpdate will start a new central Pod, while the old keeps running until the new Pod is ready. | ||
| The cluster needs to provide sufficient resources to accomodate the transition phase. |
4 participants
The Central CR for the operator has an additonal field
central.rolloutStrategy, which enables activation of RollingUpdates for the central deployment instead of Recreate.This field is documented with this PR.
Version(s):
Issue:
Feature: https://redhat.atlassian.net/browse/ROX-33759
Doc ticket: https://redhat.atlassian.net/browse/ROX-34999
Link to docs preview:
QE review:
Additional information: