Last changed
Get notified of upcoming product changes, critical vulnerability notifications and patches and more.
Sign InChainguard Images are regularly-updated, minimal container images with low-to-zero CVEs.
This image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard registry.
There are two recommended methods for installing Argo CD: using helm
and raw manifests. Chainguard's Argo CD Image is designed to be a drop-in replacement for either method.
To use this Image, replace the appropriate image:
value with the Chainguard Argo CD Image. The following is an example how such a value might appear within a Helm chart:
Based on these values, you would install Argo CD using the following helm
commands. First, add the Argo Helm repository:
Then you can install Argo CD:
Note that this example uses multiple container images, namely argocd-fips
and argocd-repo-server-fips
. Refer to the following components section for more information.
Optionally, you can use other Chainguard Images to replace Argo CD dependencies:
Argo CD is comprised of multiple components that all share the same container image.
Keeping in line with the philosophy of minimal dependencies in Chainguard Images, we chose to split this up to keep the number of packages in each respective component to a minimum. This means the overall number of images increases, but the size and complexity of each image is reduced down to the minimum needed to function.
Argo CD Repo Server has ability to use GnuPG signature verification, see upstream documentation. Chainguard does not currently have FIPS CVMP certification for gpg
. The cgr.dev/chainguard/argocd-repo-server-fips
image has environment variable ARGOCD_GPG_ENABLED=false
set, which should also be used for FIPS deployments.
If you have a Zendesk account (typically set up for you by your Customer Success Manager) you can reach out to Chainguard's Customer Success team through our Zendesk portal.
Chainguard Images are a collection of container images designed for security and minimalism.
Many Chainguard Images are distroless; they contain only an open-source application and its runtime dependencies. These images do not even contain a shell or package manager. Chainguard Images are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a secure software supply chain.
The main features of Chainguard Images include:
-dev
VariantsAs mentioned previously, Chainguard’s distroless Images have no shell or package manager by default. This is great for security, but sometimes you need these things, especially in builder images. For those cases, most (but not all) Chainguard Images come paired with a -dev
variant which does include a shell and package manager.
Although the -dev
image variants have similar security features as their distroless versions, such as complete SBOMs and signatures, they feature additional software that is typically not necessary in production environments. The general recommendation is to use the -dev
variants only to build the application and then copy all application artifacts into a distroless image, which will result in a final container image that has a minimal attack surface and won’t allow package installations or logins.
That being said, it’s worth noting that -dev
variants of Chainguard Images are completely fine to run in production environments. After all, the -dev
variants are still more secure than many popular container images based on fully-featured operating systems such as Debian and Ubuntu since they carry less software, follow a more frequent patch cadence, and offer attestations for what they include.
To better understand how to work with Chainguard Images, we encourage you to visit Chainguard Academy, our documentation and education platform.
Chainguard Images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" version of this image:
Apache-2.0
GCC-exception-3.1
GPL-2.0-only
GPL-2.0-or-later
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreementThis is a FIPS validated image for FedRAMP compliance.
This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.
Learn more about STIGsGet started with STIGs