From be9d7567be0337dc9d706b2a9f075055ac29bc60 Mon Sep 17 00:00:00 2001 From: lostsquirrel Date: Fri, 14 Aug 2020 10:15:16 +0800 Subject: [PATCH] This should not be shell the code is yaml --- content/en/docs/concepts/workloads/controllers/replicaset.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md index dd9196e814..15a9918a1c 100644 --- a/content/en/docs/concepts/workloads/controllers/replicaset.md +++ b/content/en/docs/concepts/workloads/controllers/replicaset.md @@ -245,9 +245,10 @@ For the template's [restart policy](/docs/concepts/workloads/Pods/pod-lifecycle/ The `.spec.selector` field is a [label selector](/docs/concepts/overview/working-with-objects/labels/). As discussed [earlier](#how-a-replicaset-works) these are the labels used to identify potential Pods to acquire. In our `frontend.yaml` example, the selector was: -```shell + +```yaml matchLabels: - tier: frontend + tier: frontend ``` In the ReplicaSet, `.spec.template.metadata.labels` must match `spec.selector`, or it will