Mirroring Netdata Cloud On-Prem image registry

Before You Begin

This document is only applicable to those who need to mirror our ECR repository because their environment does not allow external image repository access. Keep in mind that it also forces administrators to remember about image upgrades in their mirrored repositories on their own.

Required Components

You need AWS CLI installed and a tool that can pull, push, and manipulate images - in this example we use Docker.

Step by Step Guide to prepare images

warning

These steps need to be repeated for every image used in the netdata-cloud-onprem Helm chart.

Step 1: Configure AWS CLI

Set up your AWS credentials to access the ECR repository containing the Docker images.

Option 1: Environment Variables

export AWS_ACCESS_KEY_ID=<your_secret_id>
export AWS_SECRET_ACCESS_KEY=<your_secret_key>

Option 2: Interactive Setup

aws configure

Step 2: Configure Docker for ECR Access

Generate a token for ECR access to allow Docker to pull images from the secured repository:

aws ecr get-login-password --region us-east-1 | docker login --username AWS --password-stdin 362923047827.dkr.ecr.us-east-1.amazonaws.com

It should return Login Succeeded.

Step 3: Pull the images

Pull the required images to your local store:

docker pull 362923047827.dkr.ecr.us-east-1.amazonaws.com/<image>:<tag>

You can validate this operation by using:

docker image list

Step 4: Change the image tag

The image tag provides information about where the image came from. By changing the image tag, you can instruct Docker to push the image to a different repository.

docker tag <org_tag> <destination_tag>

For example:

docker tag 362923047827.dkr.ecr.us-east-1.amazonaws.com/onprem-cloud-frontend:latest my.image.registry/onprem-cloud-frontend:latest

Step 5: Push the re-tagged image to your repository

docker push my.image.registry/onprem-cloud-frontend:latest

Additional Steps (optional)

Netdata also provides:

• Image signatures
• Software Bill of Materials (SBOM)