Use OCI mediaTypes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
Feature request
It should be possible to use the tkn bundle push command to generate an Image Manifest with the OCI media type. Since these bundle images are not traditional container images, let's consider using artifactType.
Use case
The OCI standard clearly defines how artifacts should be described in an OCI registry. The docker media types do not. This is about more accurately representing the content.
UI Example
Ideally, by default the updated tkn bundle push command pushes an OCI artifact to the registry. A flag, e.g. --legacy, could be added if necessary to produce a docker image manifest.
(The command is marked as experimental, so maybe we don't have to worry about legacy behavior.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the tkn bundle push entry point and trace how its bundle image manifest is generated and pushed. Compare that behavior with the linked OCI manifest and artifactType guidance; done means default OCI artifact output and a defined compatibility path for legacy Docker manifests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100