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
Copy file name to clipboardExpand all lines: Decisions/scs-XXXX-v1-requirements-for-container-registry.md
+26-20Lines changed: 26 additions & 20 deletions
Original file line number
Diff line number
Diff line change
@@ -245,31 +245,37 @@ have and also a set of desirable (nice to have) features are defined and evaluat
245
245
- Additional artifacts that the registry is able to store in addition to OCI artifacts, e.g. Java, Node.js, or Python packages
246
246
- Integration possibilities
247
247
- Ability to cooperate with another software solution in order to improve own feature set (e.g. integration of P2P solution for improving container image distribution (download speed and stability, high scalability ...))
248
+
- Deployment capabilities
249
+
- How could be a container registry deployed (only "official" ways are mentioned)
250
+
- Administration capabilities "as a code"
251
+
- Ability to manage container registry via "as a code" solutions, e.g. Ansible role
248
252
249
253
Refer to the table of evaluated projects with their features. Note that only container
250
254
registry implementations that passed the OSS health stage (Harbor, Quay, and Dragonfly)
- Harbor announced the deprecation of [Notary](https://github.com/goharbor/harbor/discussions/16612) and [Chartmuseum](https://github.com/goharbor/harbor/discussions/15057)
0 commit comments