k8s-triage-robot
commented
7 months ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
MShekow
What would you like to be added?
It would be great if the
kubernetes-dashboardHelm chart could also be made available as OCI artifact on some Docker image registry of your choice (e.g. Docker Hub, quay, GitHub container registry, ...). Helm officially supports the OCI format for charts for a while now.Why is this needed?
The use case are big corporations where CI/CD systems cannot access the internet freely and instead use something like a Harbor pull-through mirror for Docker images. But Harbor does not offer properly continuously synchronized pull-through mirrors for Helm charts using the ChartMuseum-format. Once the kubernetes-dashboard chart is available as Docker image, this problem would be solved. Also, Harbor is going to deprecate ChartMuseum entirely at some point in the future.