Skip to content
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.

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

Harbor Image Replication with AWS ECR using Vault-injected Kubernetes Secrets #21064

Open
rmrj opened this issue Oct 18, 2024 · 1 comment
Open
Assignees
Labels

Comments

@rmrj
Copy link

rmrj commented Oct 18, 2024

Hi,

I'm setting up image replication between AWS ECR and a Harbor registry (v2.9.1-5cbb1b01) deployed via Helm charts.

Instead of using the Harbor UI for proxy caching, I want to leverage Vault for secure management and injection of ECR credentials through Kubernetes secrets.

Here's the plan:

  1. Store ECR credentials securely in Vault.
  2. Dynamically fetch these credentials from Vault at runtime.
  3. Make the fetched credentials available as Kubernetes secrets.
  4. Configure Harbor to use these secrets for image replication with AWS ECR.
  5. My question:

How can I configure Harbor to work with this setup?

I've reviewed the Harbor Helm chart code (https://github.com/kubeshop/helm-charts) but haven't found a way to define AWS ECR registry details.

Guidance Needed:

Can Harbor be configured to consume credentials from Kubernetes secrets for image replication?
Are there any alternative approaches to achieve this scenario using Helm charts?

Thanks,
Rama

@ianseyer
Copy link

I would setup your external registry and replication jobs via terraform: https://registry.terraform.io/providers/goharbor/harbor/latest/docs/resources/registry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants