We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent 5c456a4 commit 953d5fdCopy full SHA for 953d5fd
docs/adr/artifacts.md
@@ -26,8 +26,8 @@ decided to not use a plain http-server but an internal OCI registry to store and
26
the OCM controllers as single layer OCI artifacts.
27
28
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
+- In comparison to the current plain http-server that requires an implementation of access, GC, ... the usage of an OCI registry
+could simplify the implementation (e.g. deleting dangling blobs after a manifest was deleted)
31
- Stop support at the level of the distribution spec of OCI
32
- We will need an abstraction that handles OCI registries anyway to convert resources into a flux consumable format
33
(= single layer oci artifact)
0 commit comments