upstream/helm
1
0
Fork 0
mirror of https://github.com/helm/helm.git synced 2026-05-28 04:35:48 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

docs(templates): fix and expand config checksum example

Browse source
This commit is contained in:
Joan Rieu 2017-10-30 23:08:50 +01:00 committed by GitHub
parent e464479cb2
commit 25e851ecd0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/charts_tips_and_tricks.md
View file

@ -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