Time helm-chart release after image release
woehrl01 opened this issue · 9 comments
Is your feature request related to a problem?/Why is this needed
Describe the solution you'd like in detail
It would be great if the helm release/ github release would be promoted only after the image is actually available in the upstream repository (kubernetes/k8s.io#6282)
Describe alternatives you've considered
Additional context
If you are using automations like Renovate, releases are shown and suggested pretty fast, this results often in failing PRs because of missing images.
Agreed, I was actually about to write an issue before I saw this. This is the 3rd or 4th time I've been bit by the image not being ready before the helm chart was pushed.
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
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
/remove-lifecycle rotten