Spike: Is it possible to promote images that weren't built by a Google Cloud Build
Opened this issue · 6 comments
Objective
- SIG reaches a decision based on data that shows what's realistic.
- In the future, SIG uses this decision to plan future work.
Tasks to achieve the objective
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
Context and things to think about while working on this task
- 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"
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
/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:
- 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
/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:
- 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
/remove-lifecycle stale