Support resource fetching from OCI artifacts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
From https://github.com/coreos/ignition/pull/1923#issuecomment-4132246401:
Tangentially on this but Ignition still doesn't support fetching from OCI, right? IMO defining an OCI artifact format for Ignition and supporting fetching from it should actually become the default flow even. Nowadays there's so many good tools for OCI artifacts.
And the key here is: OCI is already cloud/platform independent and most IaaS systems support registry-as-service as well - we don't need per-hypervisor secrets for that.
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
No source file or test is named. Start by reading the linked PR discussion and issue text to understand the proposed OCI artifact format and fetching entry point; done means Ignition supports the agreed resource-fetching flow from an OCI registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100