Skip to content

docs: refine content for container registries configuration #156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 23, 2025
Merged

docs: refine content for container registries configuration #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions ...11111111/configure-argo-cd-image-updater-challenge/content/registries/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,17 @@
---
id: "registries"
title: 'Registries'
title: "Registries:"
description: ""
weight: 4
---

### Configuring the container registries
### Configuring Container Registries

Let's configure the container registries that we are using. Argo CD Image Updater supports the majority of container registries (public and private), that implement Docker registry v2 API and has been tested against registries such as Docker Hub, Docker Registry v2 reference implementation (on-premise), Red Had Quay, Jfrog Artifactory, Github Container Registry, GitHub Packages Registry, GitLab Container Registry, and Google Container Registry.
Let's configure the container registries that we are using. Argo CD Image Updater supports most container registries (public and private) that implement Docker registry v2 API and has been tested against registries such as Docker Hub, Docker Registry v2 reference implementation (on-premise), Red Hat Quay, Jfrog Artifactory, GitHub Container Registry, GitHub Packages Registry, GitLab Container Registry, and Google Container Registry.

In the following examples, we will configure two of the most widely used container registries – Amazon Elastic Container Registry (ECR) and GitHub Container Registry (GHCR). In our case, we are working with private registries to ensure secure storage and access control for container images.
In the following examples, we will configure two of the most widely used container registries: Amazon Elastic Container Registry (ECR) and GitHub Container Registry (GHCR). In our case, we are working with private registries to ensure secure storage and access control for container images.

### Amazon Elastic Container Registry (ECR) configuration
### Amazon Elastic Container Registry (ECR) Configuration

```yaml
registries:
Expand All @@ -28,9 +28,9 @@ For Amazon Elastic Container Registry, authentication is possible through a scri

```yaml
authScripts:
# -- Whether to mount the defined scripts that can be used to authenticate with a registry, the scripts will be mounted at `/scripts`
# -- Whether to mount the defined scripts that can be used to authenticate with a registry. The scripts will be mounted at `/scripts`
enabled: true
# -- Map of key-value pairs where the key consists of the name of the script and the value the contents
# -- Map of key-value pairs where the key consists of the name of the script and the value is its content.
scripts:
login.sh: |
#!/bin/sh
Expand Down Expand Up @@ -63,7 +63,7 @@ The script is executed by the pod and is responsible for obtaining the ECR autho
}
```

### Github Container Registry configuration
### Github Container Registry Configuration

```yaml
registries:
Expand All @@ -77,7 +77,7 @@ registries:
credentials: secret:argocd/ghcr-secret#token
```

For registry authentication, in the credentials section, we are using a Kubernetes secret. The **#token** part refers to the specific key (usually containing a personal access token or authentication token) inside the secret. The token must have at least **read:packages** permissions. Here is a manifest of the Kubernetes secret which has to be applied in the **argocd** namespace:
For registry authentication, in the credentials section, we are using a Kubernetes secret. The **#token** part refers to the specific key (usually containing a personal access token or authentication token) inside the secret. The token must have at least **read:packages** permission. Here is a manifest of the Kubernetes secret which has to be applied in the **argocd** namespace:

```yaml
apiVersion: v1
Expand Down