Merge pull request #2088 from weaveworks/helm/docs-clearify-fqin

Explicitly state requirements for automated `HelmRelease`s
fluxcd · May 23, 2019 · 5e17cd5 · 5e17cd5
2 parents 5b15a94 + 1c1bf10
commit 5e17cd5
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/site/helm-integration.md b/site/helm-integration.md
@@ -249,6 +249,10 @@ If the chart you're using in a `HelmRelease` lets you specify the
 particular images to run, you will usually be able to update them with
 Flux, the same way you can with Deployments and so on.
 
+> **Note:** for automation to work, the repository _and_ tag should be
+> defined, as Flux determines image updates based on what it reads in
+> the `.spec.values` of the `HelmRelease`.
+
 Flux interprets certain commonly used structures in the `values`
 section of a `HelmRelease` as referring to images. The following
 are understood (showing just the `values` section):