Skip to content

Fix bullet points #371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
IanKWatts merged 1 commit into from
Sep 1, 2026
Merged

Fix bullet points #371

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/docs/automation-and-resiliency/argo-cd-image-updater.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,13 +25,15 @@ You probably won't have to make any changes to the application configuration unl

## Update methods
Argo CD keeps track of image updates using one of two methods:

* `argocd` - (default) Image status is written to the Argo CD application.
* `git` - Image status is written to a new file in the app's Git repository.

For now, because the image updater controller has not been granted write access to your GitOps repo, **only the 'argocd' option is available**.

## Update strategies
Update strategies determine how Argo CD will look for new versions of an image.

* `semver` - (Default) Update to semantic versions
* `newest-build` - Update to the most recently built image
* `digest` - Use the most recent pushed version of a given tag, such as "latest"
Expand Down
Loading