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.

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

WIP: Proof of concept: introduce experimental OCI artifact source behind feature gate #95

Closed
wants to merge 4 commits into from

Conversation

joelanford
Copy link
Member

@joelanford joelanford commented Jun 15, 2023

This PR demonstrates the ability of catalogd to consume catalogs stored as OCI Artifacts, as produced by https://github.com/joelanford/olm-oci

In theory, we should be able to:

  • install catalogd from this PR (with the OCIArtifactSource feature gate enabled)
  • install operator-controller with a tweak that uses artifact type in rukpak Bundle (TODO)
  • install rukpak from OCI Artifacts Source rukpak#609

And then be able to begin using OCI artifact-based catalogs and bundles.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 15, 2023
…anges from default feature gates

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 21, 2023
@openshift-merge-robot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@joelanford
Copy link
Member Author

Closing since this served its purpose for demos and there are no plans to merge this.

@joelanford joelanford closed this Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants