Skip to content

Commit 98c8d4b

Browse files
authored
chore(docs): Update update strategy docs on deprecated strategy values (#1132)
Signed-off-by: Jacek Nykis <[email protected]>
1 parent 9aa87a7 commit 98c8d4b

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

docs/configuration/images.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -118,8 +118,8 @@ Argo CD Image Updater can update images according to the following strategies:
118118
|Strategy|Description|
119119
|--------|-----------|
120120
|`semver`| Update to the tag with the highest allowed semantic version|
121-
|`latest`| Update to the tag with the most recent creation date|
122-
|`name` | Update to the tag with the latest entry from an alphabetically sorted list|
121+
|`latest/newest-build`| Update to the tag with the most recent creation date|
122+
|`name/alphabetical` | Update to the tag with the latest entry from an alphabetically sorted list|
123123
|`digest`| Update to the most recent pushed version of a mutable tag|
124124

125125
You can define the update strategy for each image independently by setting the
@@ -132,14 +132,19 @@ argocd-image-updater.argoproj.io/<image_alias>.update-strategy: <strategy>
132132
If no update strategy is given, or an invalid value is used, the default
133133
strategy `semver` will be used.
134134

135+
!!!warning "Renamed image update strategies"
136+
The `latest` strategy has been renamed to `newest-build`, and `name` strategy has been renamed to `alphabetical`.
137+
Please switch to the new convention as support for the old naming convention will be removed in future releases.
138+
135139
!!!warning
136140
As of November 2020, Docker Hub has introduced pull limits for accounts on
137-
the free plan and unauthenticated requests. The `latest` update strategy
141+
the free plan and unauthenticated requests. The `latest/newest-build` update strategy
138142
will perform manifest pulls for determining the most recently pushed tags,
139143
and these will count into your pull limits. So unless you are not affected
140-
by these pull limits, it is **not recommended** to use the `latest` update
144+
by these pull limits, it is **not recommended** to use the `latest/newest-build` update
141145
strategy with images hosted on Docker Hub.
142146

147+
143148
## Filtering tags
144149

145150
You can specify an expression that is matched against each tag returned from

0 commit comments

Comments
 (0)