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
In this use case, the AWS account where the shoot is deployed, and the registry cache pod is running, already has pull access to the repositories in Amazon ECR private registry via repository policies.
Why is this needed:
We have a large number of large shoots in AWS, where services use Amazon ECR private registry as their registry to pull images from. Access to the private registry is managed via repository policies. There are no explicit credentials being used (e.g., username / password).
We would like to leverage the registry cache extension to cache images.
The text was updated successfully, but these errors were encountered:
How to categorize this issue?
/area security
/kind enhancement
What would you like to be added:
I would like the registry cache to be able to pull and cache images where
In this use case, the AWS account where the shoot is deployed, and the registry cache pod is running, already has pull access to the repositories in Amazon ECR private registry via repository policies.
Why is this needed:
The text was updated successfully, but these errors were encountered: