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

Merge pull request #20292 from rwanyoike/patch-1 

Update deployment.md - Fix inconsistency and rollback message
This commit is contained in:
Kubernetes Prow Robot 2020-04-20 20:02:55 -07:00 committed by GitHub
parent 9d09e8c0e3 db27cfd719
commit ebf3d178c4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -48,24 +48,24 @@ The following is an example of a Deployment. It creates a ReplicaSet to bring up
In this example: In this example:
* A Deployment named `nginx-deployment` is created, indicated by the `.metadata.name` field. * A Deployment named `nginx-deployment` is created, indicated by the `.metadata.name` field.
* The Deployment creates three replicated Pods, indicated by the `replicas` field. * The Deployment creates three replicated Pods, indicated by the `.spec.replicas` field.
* The `selector` field defines how the Deployment finds which Pods to manage. * The `.spec.selector` field defines how the Deployment finds which Pods to manage.
In this case, you simply select a label that is defined in the Pod template (`app: nginx`). In this case, you simply select a label that is defined in the Pod template (`app: nginx`).
However, more sophisticated selection rules are possible, However, more sophisticated selection rules are possible,
as long as the Pod template itself satisfies the rule. as long as the Pod template itself satisfies the rule.
{{< note >}} {{< note >}}
The `matchLabels` field is a map of {key,value} pairs. A single {key,value} in the `matchLabels` map The `.spec.selector.matchLabels` field is a map of {key,value} pairs. A single {key,value} in the `matchLabels` map
is equivalent to an element of `matchExpressions`, whose key field is "key" the operator is "In", is equivalent to an element of `matchExpressions`, whose key field is "key" the operator is "In",
and the values array contains only "value". and the values array contains only "value".
All of the requirements, from both `matchLabels` and `matchExpressions`, must be satisfied in order to match. All of the requirements, from both `matchLabels` and `matchExpressions`, must be satisfied in order to match.
{{< /note >}} {{< /note >}}
* The `template` field contains the following sub-fields: * The `template` field contains the following sub-fields:
* The Pods are labeled `app: nginx`using the `labels` field. * The Pods are labeled `app: nginx`using the `.metadata.labels` field.
* The Pod template's specification, or `.template.spec` field, indicates that * The Pod template's specification, or `.template.spec` field, indicates that
the Pods run one container, `nginx`, which runs the `nginx` the Pods run one container, `nginx`, which runs the `nginx`
[Docker Hub](https://hub.docker.com/) image at version 1.14.2. [Docker Hub](https://hub.docker.com/) image at version 1.14.2.
* Create one container and name it `nginx` using the `name` field. * Create one container and name it `nginx` using the `.spec.template.spec.containers[0].name` field.
Follow the steps given below to create the above Deployment: Follow the steps given below to create the above Deployment:
@ -517,7 +517,7 @@ Follow the steps given below to rollback the Deployment from the current version
The output is similar to this: The output is similar to this:
``` ```
deployment.apps/nginx-deployment deployment.apps/nginx-deployment rolled back
``` ```
Alternatively, you can rollback to a specific revision by specifying it with `--to-revision`: Alternatively, you can rollback to a specific revision by specifying it with `--to-revision`:
@ -527,7 +527,7 @@ Follow the steps given below to rollback the Deployment from the current version
The output is similar to this: The output is similar to this:
``` ```
deployment.apps/nginx-deployment deployment.apps/nginx-deployment rolled back
``` ```
For more details about rollout related commands, read [`kubectl rollout`](/docs/reference/generated/kubectl/kubectl-commands#rollout). For more details about rollout related commands, read [`kubectl rollout`](/docs/reference/generated/kubectl/kubectl-commands#rollout).
@ -1024,7 +1024,7 @@ can create multiple Deployments, one for each release, following the canary patt
## Writing a Deployment Spec ## Writing a Deployment Spec
As with all other Kubernetes configs, a Deployment needs `apiVersion`, `kind`, and `metadata` fields. As with all other Kubernetes configs, a Deployment needs `.apiVersion`, `.kind`, and `.metadata` fields.
For general information about working with config files, see [deploying applications](/docs/tutorials/stateless-application/run-stateless-application-deployment/), For general information about working with config files, see [deploying applications](/docs/tutorials/stateless-application/run-stateless-application-deployment/),
configuring containers, and [using kubectl to manage resources](/docs/concepts/overview/working-with-objects/object-management/) documents. configuring containers, and [using kubectl to manage resources](/docs/concepts/overview/working-with-objects/object-management/) documents.
The name of a Deployment object must be a valid The name of a Deployment object must be a valid