From b46f34ff3830688b01bd29eebba64e5118e0d9c3 Mon Sep 17 00:00:00 2001 From: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com> Date: Fri, 2 Aug 2019 12:57:35 +0200 Subject: [PATCH] docs: clarify that tagged images are not replaced in manifests Signed-off-by: Cornelius Weig <22861411+corneliusweig@users.noreply.github.com> --- docs/content/en/docs/how-tos/deployers/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/how-tos/deployers/_index.md b/docs/content/en/docs/how-tos/deployers/_index.md index 41cfbb32875..f8eedf49a1f 100755 --- a/docs/content/en/docs/how-tos/deployers/_index.md +++ b/docs/content/en/docs/how-tos/deployers/_index.md @@ -9,7 +9,7 @@ to deploy your app to a Kubernetes cluster. When Skaffold deploys an application the following steps happen: -* the Skaffold deployer _renders_ the final kubernetes manifests: Skaffold replaces the image names in the kubernetes manifests with the final tagged image names. +* the Skaffold deployer _renders_ the final kubernetes manifests: Skaffold replaces untagged image names in the kubernetes manifests with the final tagged image names. Also, in case of the more complicated deployers the rendering step involves expanding templates (in case of helm) or calculating overlays (in case of kustomize). * the Skaffold deployer _deploys_ the final kubernetes manifests to the cluster