Add missing default value to Progress Deadline Seconds
Potentially confusing sentence, being an optional value; not stating the default value might create an assumption that deployment will retry forever. https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.18/#deploymentspec-v1-apps
This commit is contained in:
parent
7cc3aee596
commit
ddfa877602
|
@ -1117,7 +1117,7 @@ total number of Pods running at any time during the update is at most 130% of de
|
||||||
to wait for your Deployment to progress before the system reports back that the Deployment has
|
to wait for your Deployment to progress before the system reports back that the Deployment has
|
||||||
[failed progressing](#failed-deployment) - surfaced as a condition with `Type=Progressing`, `Status=False`.
|
[failed progressing](#failed-deployment) - surfaced as a condition with `Type=Progressing`, `Status=False`.
|
||||||
and `Reason=ProgressDeadlineExceeded` in the status of the resource. The Deployment controller will keep
|
and `Reason=ProgressDeadlineExceeded` in the status of the resource. The Deployment controller will keep
|
||||||
retrying the Deployment. In the future, once automatic rollback will be implemented, the Deployment
|
retrying the Deployment. This defaults to 600. In the future, once automatic rollback will be implemented, the Deployment
|
||||||
controller will roll back a Deployment as soon as it observes such a condition.
|
controller will roll back a Deployment as soon as it observes such a condition.
|
||||||
|
|
||||||
If specified, this field needs to be greater than `.spec.minReadySeconds`.
|
If specified, this field needs to be greater than `.spec.minReadySeconds`.
|
||||||
|
|
Loading…
Reference in New Issue