From 4246a741493d6ff12bcbc6d78a8548660f815b45 Mon Sep 17 00:00:00 2001 From: Andrew Phillips Date: Tue, 10 Sep 2019 10:53:27 -0400 Subject: [PATCH] 'imagetag' -> 'image' in edit set command examples 'imagetag' is not/no longer supported as a command Kubernetes-commit: 5a753a834f350d62c2258adfd9983614c8072e88 --- docs/book/pages/app_management/container_images.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/book/pages/app_management/container_images.md b/docs/book/pages/app_management/container_images.md index 13437210..8c5c63e6 100644 --- a/docs/book/pages/app_management/container_images.md +++ b/docs/book/pages/app_management/container_images.md @@ -169,13 +169,13 @@ then the container image would be `foo:1bb359ccce344ca5d263cd257958ea035c978fd3` A simple way to push an image that was just built without manually updating the image tags is to download the [kustomize standalone](https://github.com/kubernetes-sigs/kustomize/) tool and run -`kustomize edit set imagetag` command to update the tags for you. +`kustomize edit set image` command to update the tags for you. **Example:** Set the latest git commit SHA as the image tag for `foo` images. {% sample lang="yaml" %} ```bash -kustomize edit set imagetag foo:$(git log -n 1 --pretty=format:"%H") +kustomize edit set image foo:$(git log -n 1 --pretty=format:"%H") kubectl apply -f . ``` {% endmethod %}