Application configuration¶
In order for ArgoCD Image Updater to know which applications it should inspect
for updating the workloads' container images, the corresponding Kubernetes
resource needs to be correctly annotated. ArgoCD Image Updater will inspect
only resources of kind application.argoproj.io
, that is, your ArgoCD
Application
resources. Annotations on other kinds of resources will have no
effect and will not be considered.
For its annotations, ArgoCD Image Updater uses the following prefix:
argocd-image-updater.argoproj.io
As explained earlier, your ArgoCD applications must be of either Kustomize
or Helm
type. Other types of applications will be ignored.
So, in order for ArgoCD Image Updater to consider your application for the update of its images, at least the following criteria must be met:
-
Your
Application
resource is annotated with the mandatory annotation ofargocd-image-updater.argoproj.io/image-list
, which contains at least one valid image specification (see Images Configuration). -
Your
Application
resource is of typeHelm
orKustomize
An example of a correctly annotated Application
resources might look like:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
annotations:
argocd-image-updater.argoproj.io/image-list: gcr.io/heptio-images/ks-guestbook-demo:^0.1
name: guestbook
namespace: argocd
spec:
destination:
namespace: guestbook
server: https://kubernetes.default.svc
project: default
source:
path: helm-guestbook
repoURL: https://github.com/argocd-example-apps/argocd-example-apps
targetRevision: HEAD