-
Notifications
You must be signed in to change notification settings - Fork 130
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
Please publish to OCI #758
Comments
@Ornias1993 what do you mean
|
What I mean with http based charts, is every chart system with repo's that are not OCI based. I think that's quite obvious though... As there are only three helm repo options: http(s), file and OCI It's not really relevant either, as i'm requesting OCI distribution. I get the feeling there is a language issue here, so I would suggest offloading to a native english-maintainer... |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Is your feature request related to a problem?/Why is this needed
OCI is slowly becoming the go-to standard for helm charts.
Having http based charts in-between (over)complicates dependency management.
Describe the solution you'd like in detail
Publish to OCI, for example: GHCR is a viable option
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: