sealed-secrets
sealed-secrets copied to clipboard
bitnami-labs
Publish images to ECR Public gallery
Which component: Controller
Is your feature request related to a problem? Please describe. We would like to use ECR's pull-through cache to ensure there's a copy of the Sealed Secrets controller image that's always available to us within AWS. Their pull-through cache currently does not support Docker Hub, it only supports Quay and ECR Public so since the migration to Docker Hub we've lost this option.
Describe the solution you'd like
Bitnami already publishes a ton of their images to the ECR Public gallery (link) and I believe they are an official partner, so it would be great if the sealed-secrets-controller image could be published there too.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
@alemorcuq can we get the stale label permanently removed? (sorry for the tag if you're not the right person, I just grabbed the name of someone with recent commits)
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 7 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.