Skip to content

Commit 953d5fd

Browse files
committed
Clarify advantage of storage migration wrt OCI registry
1 parent 5c456a4 commit 953d5fd

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/adr/artifacts.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ decided to not use a plain http-server but an internal OCI registry to store and
2626
the OCM controllers as single layer OCI artifacts.
2727

2828
Arguments:
29-
- In comparison to a plain http-server that requires an implementation of access, GC, ... the usage of an OCI registry
30-
would simplify the implementation
29+
- In comparison to the current plain http-server that requires an implementation of access, GC, ... the usage of an OCI registry
30+
could simplify the implementation (e.g. deleting dangling blobs after a manifest was deleted)
3131
- Stop support at the level of the distribution spec of OCI
3232
- We will need an abstraction that handles OCI registries anyway to convert resources into a flux consumable format
3333
(= single layer oci artifact)

0 commit comments

Comments
 (0)