-
Feature Request
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
-
1. Proposed title of this feature request
Make Red Hat Quay a Artifact repository
2. What is the nature and description of the request?
Customers today very much appreciate the capabilities that Red Hat Quay is offering but are unable to adopt the product because it's missing capabilities to store non OCI artifacts.
Given that other products in the market are offering these capabilities, it would be nice if Red Hat Quay could also provide a way to store and manage none OCI compliant artifacts as it would help to centralize those artifacts onto one product and use it for all the different kind of artifacts (such as Container Images, Helm Charts, Java, Python, NodeJS, etc. artifacts). We also have an ability to introduce first class UX for new artifact types like ML/LLM models.
3. Why does the customer need this? (List the business requirements here)
Right now, customers are required to run different tools in parallel, to manage the different kind of artifacts, which is cost intensive, requires lots of resources and also different knowledge, which is also expensive and difficult to maintain.
Having Red Hat Quay supporting all possible artifacts would eliminate the need of running multiple tools in parallel and instead offer a single solution, customers can standardize on and therefore reduce cost of maintenance and complexity.
4. List any affected packages or components.
Red Hat Quay
- is related to
-
PROJQUAY-7627 Make Red Hat Quay a Artifact repository
- New