diff --git a/docs/basics/update.md b/docs/basics/update.md index 4a258a33..ab430f71 100644 --- a/docs/basics/update.md +++ b/docs/basics/update.md @@ -18,7 +18,7 @@ The workflow of Argo CD Image Updater can be described as follows: annotation holds a list of image names that should be updated, and is a mandatory annotation for Argo CD Image Updater to indicate it should process this `Application`. Read more about the syntax expected in this - annotation's value in the [marking images for update](#TODO) + annotation's value in the [marking images for update](../configuration/images.md) section in this doc. * For each image found in the list, Argo CD Image Updater will first check @@ -26,19 +26,19 @@ The workflow of Argo CD Image Updater can be described as follows: check for the complete image name, including the registry the image is pulled from. For example, `docker.io/some/image` and `quay.io/some/image`, while both referring to `some/image`, are not considered equal. This strict - behavior can be relaxed, however. See [forcing image updates](#TODO) for + behavior can be relaxed, however. See [forcing image updates](../configuration/images.md#forcing-image-updates) for further explanation. * 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](../basics/update-strategies.md) + [update strategy](./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](../basics/update-methods.md). Please note that Argo CD Image Updater will + [update method](./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. @@ -49,7 +49,7 @@ images (and multi-arch clusters) by being able to inspect images with multiple manifests (i.e. a manifest list). Multi-arch currently only is supported for -[update strategies](../basics/update-strategies.md) +[update strategies](./update-strategies.md) which fetch image meta-data: `latest` and `digest`. Multi-arch will be ignored for the update strategies that do not fetch meta-data, `semver` and `name`.