Skip to content

Commit d0d1690

Browse files
kostis-codefreshmcfearsome
authored andcommitted
docs: Added warning about existing tag in semver (argoproj-labs#471)
Signed-off-by: Kostis Kapelonis <[email protected]> Signed-off-by: Kostis Kapelonis <[email protected]>
1 parent 077d0f7 commit d0d1690

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

docs/basics/update-strategies.md

+6
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,10 @@ The above example would update to any new tag pushed to the registry matching
7777
this constraint, e.g. `1.2.5`, `1.2.12` etc, but not to a new minor version
7878
(e.g. `1.3`).
7979
80+
!!!warning "A note on the current image tag"
81+
For semver strategy to work, the current application tag must already follow
82+
semver. Otherwise no comparison can happen by the updater. See discussion at [#270](https://github.com/argoproj-labs/argocd-image-updater/issues/270) for more details.
83+
8084
Likewise, to allow updates to any minor release within the major version `1`,
8185
use
8286
@@ -101,6 +105,8 @@ Image Updater will pick the highest version number found in the registry.
101105
Argo CD Image Updater will omit any tags from your registry that do not match
102106
a semantic version when using the `semver` update strategy.
103107

108+
109+
104110
### <a name="strategy-latest"></a>latest/newest-build - Update to the most recently built image
105111

106112

0 commit comments

Comments
 (0)