Open zachcasper opened 2 months ago
:wave: @zachcasper Thanks for filing this feature request.
A project maintainer will review this feature request and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
:+1: We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
Overview of feature request
Enterprises use a variety of container registries dependent upon their needs and priorities. Container registries differentiate themselves on factors mostly outside of Radius' scope such as vulnerability scanning, image curation, garbage collection, hosting method, and cross-region replication. Radius needs to be validated against registries in addition to today's GHCR testing.
p0 – Cloud platform's built-in registry: ACR, ECR private, and Google Artifact Registry when GCP is supported by Radius p1 – DevOps platform's built-in registry: GHCR, GitLab, Docker Hub p2 – Self-hosted container registries: Quay, Artifactory, Harbor
Acceptance criteria
p0 and p1 container registries are tested to work with Radius using the preferred authentication method of each registry; e.g., ECR should use an authentication token and not simply username/password.
Additional context
No response
Would you like to support us?
AB#13149