From 89f105390d3f530b04619e01d6488bd637cfd9be Mon Sep 17 00:00:00 2001 From: Max Jonas Werner Date: Thu, 25 Aug 2022 13:08:44 +0200 Subject: [PATCH] Fix note about ReplicaSet names The RS name is always derived from the hash of the pod template and it's not random. --- content/en/docs/concepts/workloads/controllers/deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/deployment.md b/content/en/docs/concepts/workloads/controllers/deployment.md index 962313f017..441fd63571 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -121,8 +121,8 @@ Follow the steps given below to create the above Deployment: * `READY` displays how many replicas of the application are available to your users. * `AGE` displays the amount of time that the application has been running. - 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. + Notice that the name of the ReplicaSet is always formatted as `[DEPLOYMENT-NAME]-[HASH]`. + The `HASH` string is the same as the `pod-template-hash` label on the ReplicaSet. 6. To see the labels automatically generated for each Pod, run `kubectl get pods --show-labels`. The output is similar to: