From f1ffcd696cddc28fbfa195ec42213e2ea18eea00 Mon Sep 17 00:00:00 2001 From: Marek Biskup Date: Tue, 26 May 2015 18:30:08 +0200 Subject: [PATCH] typo fix in rolling-update linkswq --- docs/secrets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/secrets.md b/docs/secrets.md index 3ac8d1c3c2..019e9350f3 100644 --- a/docs/secrets.md +++ b/docs/secrets.md @@ -89,8 +89,8 @@ Once a pod is created, its secret volumes will not change, even if the secret resource is modified. To change the secret used, the original pod must be deleted, and a new pod (perhaps with an identical PodSpec) must be created. Therefore, updating a secret follows the same workflow as deploying a new -container image. The `kubectl rollingupdate` command can be used ([man -page](kubectl-rollingupdate.md)). +container image. The `kubectl rolling-update` command can be used ([man +page](kubectl_rolling-update.md)). The resourceVersion of the secret is not specified when it is referenced. Therefore, if a secret is updated at about the same time as pods are starting,