kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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:
Fuxing Loh 2020-04-25 09:26:26 +08:00
parent 7cc3aee596
commit ddfa877602
No known key found for this signature in database
GPG Key ID: 939E089828E48221
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/workloads/controllers/deployment.md
View File

@ -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
[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
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.
If specified, this field needs to be greater than `.spec.minReadySeconds`.