Skip to content

Commit 9e83fe5

Browse files
Update _index.md
Signed-off-by: Aryan Shah <[email protected]>
1 parent aed79c1 commit 9e83fe5

File tree

1 file changed

+2
-2
lines changed
  • content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/update-strategies

1 file changed

+2
-2
lines changed

content/challenges/11111111-1111-1111-1111-111111111111/configure-argo-cd-image-updater-challenge/content/update-strategies/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ sampleapp:
7474
pullPolicy: "Always"
7575
```
7676
77-
### latest upadte strategy:
77+
### latest update strategy:
7878
7979
Argo CD Image Updater can update the image with the most recent build date, even if the tag is arbitrary (like a Git commit SHA or random string). It focuses on the build date, not when the image was tagged or pushed to the registry. If multiple tags share the same build date, the updater sorts the tags in descending lexical order and selects the last one.
8080
@@ -197,4 +197,4 @@ After we’ve made the needed configurations and selected the most suitable upda
197197
198198
![update-strategy-1](update-strategy-1.jpg)
199199
200-
As we can see, after the new image version was pushed in ECR, the original value of the image tag was changed by the Argo CD image updater, and the new image was deployed!
200+
As we can see, after the new image version was pushed in ECR, the original value of the image tag was changed by the Argo CD image updater, and the new image was deployed!

0 commit comments

Comments
 (0)