diff options
| author | claudex <claude.xavier@gmail.com> | 2022-11-16 04:36:31 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-11-15 22:36:31 -0500 |
| commit | cd5907445176b886a800566b0b65c2e8ab456d5c (patch) | |
| tree | 3a29e9fa21638995715a0baf649dd6e559e5b706 /docs | |
| parent | 70687253f673455c027cc009863ebd38a4ec68b8 (diff) | |
docs: Fix dead links (#434)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/basics/update.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/basics/update.md b/docs/basics/update.md index 30da0f7..9e23f4a 100644 --- a/docs/basics/update.md +++ b/docs/basics/update.md @@ -32,13 +32,13 @@ The workflow of Argo CD Image Updater can be described as follows: * If Argo CD Image Updater considers an image from the list eligible for an update check, it will connect the corresponding container registry to see if there is a newer version of the image according to the - [update strategy](../strategies/) + [update strategy](../update-strategies/) and other constraints that may have been configured for the image (e.g. a list of tags that are allowed to consider). * If a newer version of an image was found, Argo CD Image Updater will try to update the image according to the configured - [update method](../methods/). Please note that Argo CD Image Updater will + [update method](../update-methods/). Please note that Argo CD Image Updater will never update your manifests, instead it re-configures your Application sources to use the new image tag, and control is handed over to Argo CD. |