[Umbrella Issue] Setup a GCS Bucket for projects to use

[dims]

Please see

• https://docs.google.com/document/d/1cQUAU3AeRahL8Y4R6BDiMiMV44ESPDFNyZQIlgSA5eQ/edit#heading=h.oa3xwm42jn26
• kep: image promoter: process to copy container images community#2695

[dims]

cc @thockin @mkumatag @javier-b-perez @listx

[javier-b-perez]

Added some comments in the doc, LGTM

[listx]

LGTM

[dims]

cc @mkumatag @thockin

[dims]

• Separate out GCS buckets for say kops binaries.
• Need separate GCR as well for images

[dims]

Let's use this for GCS buckets. will create another issue for GCR container images repo

[ixdy]

I think @spiffxp meant to
/assign @thockin @dims
here

[BenTheElder]

cc

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
Its not clear to me that breaking out issues for GCS, GCR, etc. really maps well to the work that is ongoing. Will revisit this

[spiffxp]

Via the scripts: anyone who creates a "staging repo" gets both a GCS bucket and GCR repo now

[dims]

/unassign

[spiffxp]

/close
we have a set of scripts that work well for staging repos, everything else is ad-hoc (eg: release team asked for one and it was handled ad-hoc)

no individual access (other than via group)

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
we have a set of scripts that work well for staging repos, everything else is ad-hoc (eg: release team asked for one and it was handled ad-hoc)

no individual access (other than via group)

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/test-infra repository.