summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorFluder-Paradyne <121793617+Fluder-Paradyne@users.noreply.github.com>2024-05-06 15:43:36 +0530
committerCheng Fang <cfang@redhat.com>2024-05-07 13:28:03 -0400
commitbf1acbeab5768a1517bc9b6326a3470edb4c4f21 (patch)
treea57bfce0be4b29ae76a1314c3e0f6e0ff1d96eb3 /docs
parent4fd958ea1a06c12cd554a8531f17d10dbffed206 (diff)
fix path
Signed-off-by: Fluder-Paradyne <121793617+Fluder-Paradyne@users.noreply.github.com>
Diffstat (limited to 'docs')
-rw-r--r--docs/basics/update.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/basics/update.md b/docs/basics/update.md
index 623debb..4a258a3 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](../update-strategies/)
+ [update strategy](../basics/update-strategies.md)
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](../update-methods/). Please note that Argo CD Image Updater will
+ [update method](../basics/update-methods.md). 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.