From bd50474a841c81fa5e61f26d55bbbd96a7f09f8d Mon Sep 17 00:00:00 2001 From: nonylene Date: Fri, 22 Nov 2019 06:43:29 +0900 Subject: [PATCH] Fix invalid command (kubectl rolling-update) (#17607) `kubectl rolling-update` is the right command. Doc: https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller/ --- 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 71a47a4026..6e83992421 100644 --- a/content/en/docs/concepts/workloads/controllers/deployment.md +++ b/content/en/docs/concepts/workloads/controllers/deployment.md @@ -1143,9 +1143,9 @@ it is created. ## Alternative to Deployments -### kubectl rolling update +### kubectl rolling-update -[`kubectl rolling update`](/docs/reference/generated/kubectl/kubectl-commands#rolling-update) updates Pods and ReplicationControllers +[`kubectl rolling-update`](/docs/reference/generated/kubectl/kubectl-commands#rolling-update) updates Pods and ReplicationControllers in a similar fashion. But Deployments are recommended, since they are declarative, server side, and have additional features, such as rolling back to any previous revision even after the rolling update is done.