You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Store ECR credentials securely in Vault.
Dynamically fetch these credentials from Vault at runtime.
Make the fetched credentials available as Kubernetes secrets.
Configure Harbor to use these secrets for image replication with AWS ECR.
My question:
How can I configure Harbor to work with this setup?
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
The text was updated successfully, but these errors were encountered:
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:
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
The text was updated successfully, but these errors were encountered: