Deployment documentation incorrectly describes how ReplicaSets are named (#12712)
I went ahead and corrected the incorrect description, as well as some incorrect examples
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
c913a0b82d
commit
ef4e36c928
@@ -128,18 +128,19 @@ To see the ReplicaSet (`rs`) created by the deployment, run `kubectl get rs`:
|
|||||||
|
|
||||||
```shell
|
```shell
|
||||||
NAME DESIRED CURRENT READY AGE
|
NAME DESIRED CURRENT READY AGE
|
||||||
nginx-deployment-2035384211 3 3 3 18s
|
nginx-deployment-75675f5897 3 3 3 18s
|
||||||
```
|
```
|
||||||
|
|
||||||
Notice that the name of the ReplicaSet is always formatted as `[DEPLOYMENT-NAME]-[POD-TEMPLATE-HASH-VALUE]`. The hash value is automatically generated when the Deployment is created.
|
Notice that the name of the ReplicaSet is always formatted as `[DEPLOYMENT-NAME]-[RANDOM-STRING]`. The random string is
|
||||||
|
randomly generated and uses the pod-template-hash as a seed.
|
||||||
|
|
||||||
To see the labels automatically generated for each pod, run `kubectl get pods --show-labels`. The following output is returned:
|
To see the labels automatically generated for each pod, run `kubectl get pods --show-labels`. The following output is returned:
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
NAME READY STATUS RESTARTS AGE LABELS
|
NAME READY STATUS RESTARTS AGE LABELS
|
||||||
nginx-deployment-2035384211-7ci7o 1/1 Running 0 18s app=nginx,pod-template-hash=2035384211
|
nginx-deployment-75675f5897-7ci7o 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
|
||||||
nginx-deployment-2035384211-kzszj 1/1 Running 0 18s app=nginx,pod-template-hash=2035384211
|
nginx-deployment-75675f5897-kzszj 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
|
||||||
nginx-deployment-2035384211-qqcnn 1/1 Running 0 18s app=nginx,pod-template-hash=2035384211
|
nginx-deployment-75675f5897-qqcnn 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
|
||||||
```
|
```
|
||||||
|
|
||||||
The created ReplicaSet ensures that there are three `nginx` Pods running at all times.
|
The created ReplicaSet ensures that there are three `nginx` Pods running at all times.
|
||||||
@@ -1012,5 +1013,3 @@ in a similar fashion. But Deployments are recommended, since they are declarativ
|
|||||||
additional features, such as rolling back to any previous revision even after the rolling update is done.
|
additional features, such as rolling back to any previous revision even after the rolling update is done.
|
||||||
|
|
||||||
{{% /capture %}}
|
{{% /capture %}}
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user