From bf1acbeab5768a1517bc9b6326a3470edb4c4f21 Mon Sep 17 00:00:00 2001 From: Fluder-Paradyne <121793617+Fluder-Paradyne@users.noreply.github.com> Date: Mon, 6 May 2024 15:43:36 +0530 Subject: fix path Signed-off-by: Fluder-Paradyne <121793617+Fluder-Paradyne@users.noreply.github.com> --- docs/basics/update.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs') 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. -- cgit v1.2.3