whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update deployments.md

Browse Source
This commit is contained in:
devin-donnelly
2016-12-06 16:37:10 -08:00
committed by Michail Kargakis
parent a86732a455
commit 7427bc7a6a
1 changed files with 15 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/deployments.md
+15 -19
View File
@@ -461,41 +461,39 @@ it can be [complete](#complete-deployment), or it can [fail to progress](#failed
### Progressing Deployment ### Progressing Deployment
A Deployment is progressing when one of the following tasks is performed: Kubernetes marks a Deployment as _progressing_ when one of the following tasks is performed:
* the creation of the new ReplicaSet. * The Deployment is in the process of creating a new ReplicaSet.
* scaling up the new ReplicaSet. * The Deployment is scaling up an existing ReplicaSet.
* scaling down old ReplicaSets. * The Deployment is scaling down an existing ReplicaSet.
You can monitor the progress for a Deployment by using `kubectl rollout status`. You can monitor the progress for a Deployment by using `kubectl rollout status`.
### Complete Deployment ### Complete Deployment
A Deployment is complete when it has the following characteristics: Kubernetes marks a Deployment as _complete_ when it has the following characteristics:
* The Deployment has minimum availability. Minimum availability means that the Deployment's number of available replicas * The Deployment has minimum availability. Minimum availability means that the Deployment's number of available replicas
equals or exceeds the number required by the Deployment strategy. equals or exceeds the number required by the Deployment strategy.
* All of the replicas associated with the Deployment have been updated to the latest version you've specified, meaning any * All of the replicas associated with the Deployment have been updated to the latest version you've specified, meaning any
updates you've requested have been completed. updates you've requested have been completed.
TODO: Link to doc that references generation/observedGeneration
### Failed Deployment ### Failed Deployment
Your Deployment may get stuck trying to deploy its newest ReplicaSet without ever completing, due to: Your Deployment may get stuck trying to deploy its newest ReplicaSet without ever completing. This can occur due to some of the following factors:
* insufficient quota * Insufficient quota
* readiness probe failures * Readiness probe failures
* image pull error * Image pull errors
* insufficient permissions * Insufficient permissions
* limit ranges * Limit ranges
* application runtime misconfiguration * Application runtime misconfiguration
For any Pod creation or deletion failure, you will be notified with a Deployment status condition of `ReplicaFailure` For any Pod creation or deletion failure, you will be notified with a Deployment status condition of `ReplicaFailure`
type. You can also specify a deadline parameter in the spec ([spec.progressDeadlineSeconds](#progress-deadline-seconds)) type. You can also specify a deadline parameter in the spec ([spec.progressDeadlineSeconds](#progress-deadline-seconds))
that denotes the number of seconds to wait for your Deployment to report any progress. that denotes the number of seconds to wait for your Deployment to report any progress.
To make the controller report lack of progress for a Deployment after 10 minutes: The following `kubectl` command sets the spec with `progressDeadlineSeconds` to make the controller report lack of progress for a Deployment after 10 minutes:
```shell ```shell
$ kubectl patch deployment/nginx-deployment -p '{"spec":{"progressDeadlineSeconds":600}}' $ kubectl patch deployment/nginx-deployment -p '{"spec":{"progressDeadlineSeconds":600}}'
@@ -530,8 +528,7 @@ Conditions:
<...> <...>
``` ```
This is how the status of the Deployment looks like if you would run `kubectl get deployment nginx-deployment -o yaml` If you run `kubectl get deployment nginx-deployment -o yaml`, the Deployement status might look like this:
(spec of the object is omitted for brevity):
``` ```
status: status:
@@ -561,8 +558,7 @@ status:
unavailableReplicas: 2 unavailableReplicas: 2
``` ```
Eventually, once the Deployment progress deadline is exceeded, the status and reason of the Progressing condition Eventually, once the Deployment progress deadline is exceeded, Kubernetes updates the status and the reason for the Progressing condition:
will be switched:
``` ```
Conditions: Conditions: