From 7166553e722da49601de855c44e5eaf2318e6c3d Mon Sep 17 00:00:00 2001 From: Seth Date: Wed, 5 Jun 2019 22:52:11 -0700 Subject: [PATCH] Rs rollingupdate (#14462) * Redirect to Deployment docs * Redirect to Deployment docs * change using to use * typo * fix extra file * 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 3ff5e4bcb7..57880814c8 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 [rolling update](#rolling-updates). +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