kubernetes
Push dashboard helm chart to DockerHub
What would you like to be added?
I would like to extend the cd workflow to push the dashboard helm chart to ghcr for the OCI support.
Why is this needed?
Having the OCI support would enable Flux's automatic artifact update and Harbor automatic replication.
Unfortunately, it is not possible due to internal kubernetes organization policies. Our images are technically already being pushed to ghcr but we cannot make them public. If kubernetes org will revisit these policies at any point, we will change that and include helm chart too. At the moment there is nothing we can do.
/close
@floreks: Closing this issue.
In response to this:
Unfortunately, it is not possible due to internal kubernetes organization policies. Our images are technically already being pushed to ghcr but we cannot make them public. If kubernetes org will revisit these policies at any point, we will change that. At the moment there is nothing we can do.
/close
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-sigs/prow repository.
If it would help we could think about pushing our helm chart to the dockerhub (I think it should be possible too).
@floreks sounds like a good idea, how could we manage the authentication to dockerhub?
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
What would you like to be added?
I would like to extend the cd workflow to push the dashboard helm chart to ghcr for the OCI support.
Why is this needed?
Having the OCI support would enable Flux's automatic artifact update and Harbor automatic replication.
@domolitom : Can you please update the initial comment to mention dockerhub rather than ghcr? Thanks!
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:
- 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 rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages 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:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages 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 closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
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-sigs/prow repository.