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

Support OCI manifests #1099

Open
1 task done
joebowbeer opened this issue Nov 13, 2023 · 9 comments
Open
1 task done

Support OCI manifests #1099

joebowbeer opened this issue Nov 13, 2023 · 9 comments

Comments

@joebowbeer
Copy link

joebowbeer commented Nov 13, 2023

Checklist

  • I've searched the issue queue to verify this is not a duplicate feature request.

Proposed Feature

Kargo should be able to use OCI registries for k8s manifests.

This includes the ability for a stage to subscribe to manifests from an OCI registry as well as to publish rendered manifests to an OCI registry.

Motivation

In the rendered manifest pattern, the rendered manifests are artifacts and, as such, should be published to an OCI registry (e.g., ghcr).

In addition, OCI registries support signed manifests.

Suggested Implementation

ArgoCD is adding first-class support for OCI

https://github.com/argoproj/argo-cd/blob/master/docs/proposals/native-ocp-support.md

Flux already supports OCI. The flux cli can push/pull manifests to/from OCI registries.

https://fluxcd.io/flux/cheatsheets/oci-artifacts/

@krancour
Copy link
Member

Thanks for an interesting idea @joebowbeer. I think there's a lot to work through here, but I really like the idea.

Copy link

This issue has been automatically marked as stale because it had no activity for 90 days. It will be closed if no activity occurs in the next 30 days but can be reopened if it becomes relevant again.

@github-actions github-actions bot added the stale label Feb 12, 2024
@krancour
Copy link
Member

Not stale.

Copy link

This issue has been automatically marked as stale because it had no activity for 90 days. It will be closed if no activity occurs in the next 30 days but can be reopened if it becomes relevant again.

@hoopty
Copy link

hoopty commented Jun 8, 2024

@blakepettersson
Copy link
Contributor

Something being worked on atm with argoproj/argo-cd#18646

Copy link

This issue has been automatically marked as stale because it had no activity for 90 days. It will be closed if no activity occurs in the next 30 days but can be reopened if it becomes relevant again.

@github-actions github-actions bot added the stale label Nov 18, 2024
@hoopty
Copy link

hoopty commented Nov 25, 2024

Is this still in progress? We have some air gap use cases that would be nice to not have local git server dependency.

@joebowbeer
Copy link
Author

Update: The ArgoCD support is now beta

argoproj/argo-cd#18646

@github-actions github-actions bot removed the stale label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants