argocd Declarative continuous deployment for Kubernetes.
The images available on cgr.dev:
docker pull cgr.dev/chainguard/argocd
docker pull cgr.dev/chainguard/argocd-repo-server
ArgoCD provides two upstream methods for installing, helm, and raw manifests.
The Chainguard Images for ArgoCD are designed to be a drop in replacement for either method. To use them, simply replace the appropriate image: path with the Chainguard specific ArgoCD image. Below is an example values file for doing this with helm:
Using the above values, the helm commands become:
helm repo add argo https://argoproj.github.io/argo-helm
helm install argocd argo/argo-cd \
--namespace argocd \
--set global.image.repository="cgr.dev/chainguard/argocd" \
--set global.image.tag="latest" \
--set repoServer.image.repository="cgr.dev/chainguard/argocd-repo-server" \
Note the multiple images: argocd and argocd-repo-server. See the components section below for more info.
NOTE: Setting the tag to “latest” is not recommended, and only shown for illustrative purposes.
Optionally, you can use Chainguard Images to replace the other ArgoCD dependencies:
ArgoCD is comprised of multiple components that all share the same image.
Keeping in line with the philosophy of minimal components in Chainguard images, we chose to split this up to keep the number of packages in the components to a minimum. This means the overall number of images increases, but the size and complexity of each image is reduced to (almost) the bare minimum needed to function.