From 25e851ecd03301030aa76b106520a52ec2a8f44e Mon Sep 17 00:00:00 2001 From: Joan Rieu Date: Mon, 30 Oct 2017 23:08:50 +0100 Subject: [PATCH] docs(templates): fix and expand config checksum example --- docs/charts_tips_and_tricks.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/charts_tips_and_tricks.md b/docs/charts_tips_and_tricks.md index 1573f2edd..f1faca100 100644 --- a/docs/charts_tips_and_tricks.md +++ b/docs/charts_tips_and_tricks.md @@ -134,9 +134,8 @@ be updated with a subsequent `helm upgrade`, but if the deployment spec itself didn't change the application keeps running with the old configuration resulting in an inconsistent deployment. -The `sha256sum` function can be used together with the `include` -function to ensure a deployments template section is updated if another -spec changes: +The `sha256sum` function can be used to ensure a deployment's +annotation section is updated if another file changes: ```yaml kind: Deployment @@ -148,6 +147,9 @@ spec: [...] ``` +See also the `helm upgrade --recreate-pods` flag for a slightly +different way of addressing this issue. + ## Tell Tiller Not To Delete a Resource Sometimes there are resources that should not be deleted when Helm runs a