summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorKostis (Codefresh) <39800303+kostis-codefresh@users.noreply.github.com>2022-11-16 05:35:29 +0200
committerGitHub <noreply@github.com>2022-11-15 22:35:29 -0500
commit70687253f673455c027cc009863ebd38a4ec68b8 (patch)
treef7c8d0488b8f172ec66d1a6f7aa9eaacf411255d /docs
parentff82d5927d184eddd1c38174ba74f6bf17a68600 (diff)
docs: Added warning about existing tag in semver (#471)
Signed-off-by: Kostis Kapelonis <kostis@codefresh.io> Signed-off-by: Kostis Kapelonis <kostis@codefresh.io>
Diffstat (limited to 'docs')
-rw-r--r--docs/basics/update-strategies.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/basics/update-strategies.md b/docs/basics/update-strategies.md
index 0963a53..499e6c1 100644
--- a/docs/basics/update-strategies.md
+++ b/docs/basics/update-strategies.md
@@ -77,6 +77,10 @@ The above example would update to any new tag pushed to the registry matching
this constraint, e.g. `1.2.5`, `1.2.12` etc, but not to a new minor version
(e.g. `1.3`).
+!!!warning "A note on the current image tag"
+ For semver strategy to work, the current application tag must already follow
+ 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.
+
Likewise, to allow updates to any minor release within the major version `1`,
use
@@ -101,6 +105,8 @@ Image Updater will pick the highest version number found in the registry.
Argo CD Image Updater will omit any tags from your registry that do not match
a semantic version when using the `semver` update strategy.
+
+
### <a name="strategy-latest"></a>latest/newest-build - Update to the most recently built image