RFC-0003: Introduce Flux OCI media type #3575
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Given that DockerHub and all the other popular registries now support custom media type, I propose that we use
application/vnd.cncf.flux
for the artifacts created withflux push
. This change doesn't affect Flux source-controller, the controller will still work with any type of OCI artifact as long as it contains atar+gzip
layer.Instead of using the Docker distribution media types, we'll be using:
application/vnd.oci.image.manifest.v1+json
application/vnd.cncf.flux.config.v1+json
application/vnd.cncf.flux.content.v1.tar+gzip