Spike: Is it possible to promote images that weren't built by a Google Cloud Build

kubernetes-sigs / promo-tools

Container and file artifact promotion tooling for the Kubernetes project

Apache License 2.0

143 stars 72 forks source link

Open LappleApple opened 7 months ago

LappleApple commented 7 months ago

By 1-3 contributors:

[ ] What problem do we currently have with Google Cloud Build? Security, etc.?
[ ] Do research on the topic
[ ] Collect and answer additional questions as part of your research phase
[ ] Prepare a brief (1-2 pages max) proposal evaluating pros, cons, and tradeoffs
[ ] Share proposal with SIG (mailing list, Slack thread, at community meeting)

By the SIG/group:

[ ] SIG members provide input on findings/raise questions
[ ] After a timeboxed review period (to be determined), SIG members regroup to make a decision
[ ] Log decision for community awareness
[ ] Plan next steps

This relates to potential work to make the image promoter less monolithic
It specifically relates to the step, "Changes images.yaml for image in github.com/kubernetes/k8s.io"

k8s-triage-robot commented 3 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/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

xmudrii commented 3 months ago

/remove-lifecycle stale

k8s-triage-robot commented 3 weeks ago