From dd595498b44a268d0e3c68362ab58a5cdb6c0e7e Mon Sep 17 00:00:00 2001 From: Seth McCombs Date: Wed, 22 May 2019 14:06:02 +0200 Subject: [PATCH] line wrap Deployment --- content/en/docs/concepts/workloads/controllers/replicaset.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/concepts/workloads/controllers/replicaset.md b/content/en/docs/concepts/workloads/controllers/replicaset.md index f61252462a1bd..57880814c8dd9 100644 --- a/content/en/docs/concepts/workloads/controllers/replicaset.md +++ b/content/en/docs/concepts/workloads/controllers/replicaset.md @@ -281,7 +281,8 @@ curl -X DELETE 'localhost:8080/apis/extensions/v1beta1/namespaces/default/repli Once the original is deleted, you can create a new ReplicaSet to replace it. As long as the old and new `.spec.selector` are the same, then the new one will adopt the old Pods. However, it will not make any effort to make existing Pods match a new, different pod template. -To update Pods to a new spec in a controlled way, use a [Deployment](/docs/concepts/workloads/controllers/deployment/#creating-a-deployment), as ReplicaSets do not support a rolling update directly. +To update Pods to a new spec in a controlled way, use a +[Deployment](/docs/concepts/workloads/controllers/deployment/#creating-a-deployment), as ReplicaSets do not support a rolling update directly. ### Isolating Pods from a ReplicaSet