Rephrase doc about Deployment .spec.rollbackTo field
This commit is contained in:
@@ -866,13 +866,20 @@ a Pod is considered ready, see [Container Probes](/docs/concepts/workloads/pods/
|
|||||||
|
|
||||||
### Rollback To
|
### Rollback To
|
||||||
|
|
||||||
`.spec.rollbackTo` is an optional field with the configuration the Deployment is rolling back to. Setting
|
`.spec.rollbackTo` is an optional field with the configuration the Deployment
|
||||||
this field will trigger a rollback, and this field will be cleared every time a rollback is done.
|
should roll back to. Setting this field triggers a rollback, and this field will
|
||||||
|
be cleared by the server after a rollback is done.
|
||||||
|
|
||||||
|
Because this field will be cleared by the server, it should not be used
|
||||||
|
declaratively. For example, you should not perform `kubectl apply` with a
|
||||||
|
manifest with `.spec.rollbackTo` field set.
|
||||||
|
|
||||||
#### Revision
|
#### Revision
|
||||||
|
|
||||||
`.spec.rollbackTo.revision` is an optional field specifying the revision to rollback to. This defaults
|
`.spec.rollbackTo.revision` is an optional field specifying the revision to roll
|
||||||
to 0, meaning rollback to the last revision in history.
|
back to. Setting to 0 means rolling back to the last revision in history;
|
||||||
|
otherwise, means rolling back to the specified revision. This defaults to 0 when
|
||||||
|
[`spec.rollbackTo`](#rollback-to) is set.
|
||||||
|
|
||||||
### Revision History Limit
|
### Revision History Limit
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user