ArgoCD with automatic git-crypt decryption
Find a file
Renovate Bot 0fa4f4038d
All checks were successful
ci/woodpecker/pr/container_image Pipeline was successful
ci/woodpecker/pull_request_closed/container_image Pipeline was successful
ci/woodpecker/push/container_image Pipeline was successful
Update quay.io/argoproj/argocd Docker tag to v3.1.9
2025-10-17 22:15:18 +00:00
.woodpecker fix typo in CI log 2025-03-26 10:29:56 +01:00
example add deployment example 2022-07-20 21:10:42 +02:00
.gitignore setup project scaffold files 2022-07-20 19:57:06 +02:00
.pre-commit-config.yaml setup project scaffold files 2022-07-20 19:57:06 +02:00
Dockerfile Update quay.io/argoproj/argocd Docker tag to v3.1.9 2025-10-17 22:15:18 +00:00
git-wrapper.sh fix git-wrapper to not unintentionally be recursive 2022-07-20 21:01:42 +02:00
LICENSE setup project scaffold files 2022-07-20 19:57:06 +02:00
README.md update link to container image in readme 2025-06-27 13:39:57 +02:00
renovate.json setup project scaffold files 2022-07-20 19:57:06 +02:00

ArgoCD with git-crypt

This is a build-your-own-image of ArgoCD with git-crypt installed and configured to automatically decrypt repositories. This effectively enables ArgoCD users to store their secrets directly in git while not revealing them to strangers and still using ArgoCD to deploy them.

Supported ArgoCD Versions

The latest ArgoCD release is automatically rebuilt and published to the GitHub image registry. However, this really only includes the latest ArgoCD release. If you or your organisation need another version, you will have to build the image yourself or use one of the older image tags if GitHub hasn't deleted it yet.

Usage

  1. This repository contains the source Dockerfile to build an image derived from quay.io/argoproj/argocd. You can either use the Dockerfile to build your own image or use the provided image from ghcr.io/lilioid/argocd-git-crypt.

    This repository does not contain helm charts or other ArgoCD related manifests. This means that, in order to use this, you will have to follow the upstream ArgoCD instructions in order to deploy it but instead of using the normal image, you will have to use this repositories image instead for the argocd-repo-server deployment.

  2. Additionally, you will need to configure ArgoCD a bit to allow git-crypt to work correctly. To do this, create a gpg secret key and provide it to ArgoCD inside its gpg-keys volume. The file must be named like the key fingerprint. On startup, ArgoCD will automatically load all key files (public and secret) from here into a keyring.

Usage Example

An example deployment base on kustomize can be viewed inside the example folder.