Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Set up Single Layer OCI Artifacts #75

Open
5 of 14 tasks
fabianburth opened this issue Nov 26, 2024 · 0 comments · May be fixed by #98
Open
5 of 14 tasks

Set up Single Layer OCI Artifacts #75

fabianburth opened this issue Nov 26, 2024 · 0 comments · May be fixed by #98
Assignees
@frewilhelm @ikhandamirov
Labels
area/ipcei Important Project of Common European Interest
Milestone
2025-Q1

Comments

@fabianburth
Copy link
Contributor

fabianburth commented Nov 26, 2024 •
edited by frewilhelm
Loading

What would you like to be added:
Implementation for setting up single layer artifact containing the blobs (or, in other words, the content of what are currently called Artifacts).

Why is this needed:
So, in both cases described in the epic, we need an implementation to set up oci artifacts containing the corresponding blob content and store them in an oci registry. The common approach for this (which is also chosen by helm for setting up helm charts as oci artifacts) is to create single layer oci artifacts.

See #76

  • Remove openflux artifact
  • Setup/Use internal OCI registry
  • Implement Single Layer OCI artifact implementation
  • Disable e2e tests until the (Flux)Deployer is implemented
  • Make sure that OCM versions are compliant to the OCI version spec, e.g. v1.0.0+dev has to be mapped to v1.0.0.build-dev to be reachable with OCM
  • Create snapshot controller
    • Populate snapshot controller tests
  • Add tests for resource, localisation, and configuration controller to make sure the storage migration is working.
  • Resolve new TODOs
    • How to handle component descriptor lists that are already downloaded and stored in the OCI registry
    • How to handle resources that are already downloaded and stored in the OCI registry
  • Decide if we want to stay with the current test-setup that runs a zot binary locally.
    • Maybe oras in-memory storage could also be viable
  • Prepare a(n) internal demo
@github-actions github-actions bot added the area/ipcei Important Project of Common European Interest label Nov 26, 2024
@fabianburth fabianburth transferred this issue from open-component-model/ocm Nov 26, 2024
@jakobmoellerdev jakobmoellerdev moved this from 🆕 ToDo to 📋 Next-UP in OCM Backlog Board Nov 26, 2024
@fabianburth fabianburth mentioned this issue Nov 28, 2024
Closed
2 tasks
@jakobmoellerdev jakobmoellerdev self-assigned this Dec 18, 2024
@jakobmoellerdev jakobmoellerdev moved this from 📋 Next-UP to 🏗 In Progress in OCM Backlog Board Dec 18, 2024
@jakobmoellerdev jakobmoellerdev moved this from 🏗 In Progress to 📋 Next-UP in OCM Backlog Board Jan 9, 2025
@frewilhelm frewilhelm mentioned this issue Jan 9, 2025
Closed
6 tasks
This was referenced Jan 22, 2025
Draft
Open
@frewilhelm frewilhelm mentioned this issue Feb 5, 2025
Closed
9 tasks
@morri-son morri-son added this to the 2025-Q1 milestone Feb 6, 2025
@morri-son morri-son moved this from 📋 Next-UP to 🏗 In Progress in OCM Backlog Board Feb 6, 2025
@ikhandamirov ikhandamirov mentioned this issue Feb 6, 2025
Merged
ikhandamirov added a commit that referenced this issue Feb 7, 2025
@ikhandamirov
feat: in-cluster zot registry as part of deployment (#112)
61f154b 
#### What this PR does / why we need it

With this PR an in-cluster instance of `zot` OCI registry will be
deployed aside to the controllers:
* `make deploy-dev` makes `zot` accessible via http.
* `make deploy` makes `zot` accessible via https.

#### Which issue(s) this PR fixes

This PR is in the context of #75 and should be merged before #98
@ikhandamirov ikhandamirov mentioned this issue Feb 12, 2025
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@frewilhelm frewilhelm

@ikhandamirov ikhandamirov

Labels
area/ipcei Important Project of Common European Interest
Projects
OCM Backlog Board
Status: 🏗 In Progress
Milestone
2025-Q1
Development

Successfully merging a pull request may close this issue.

Implement Single Layer OCI Artifacts open-component-model/ocm-k8s-toolkit
5 participants
@frewilhelm @fabianburth @jakobmoellerdev @morri-son @ikhandamirov