audit-followup: pre-create GCR buckets for e2e projects

[spiffxp]

ref: https://github.com/kubernetes/k8s.io/pull/1903/files#r620573231

We pre-create these buckets for staging projects, we should do the same for e2e projects now that they all have GCR enabled by default (TODO: link to issue/PR that did this a few months ago)

/area prow
/area artifacts
/wg k8s-infra
/sig testing
/sig release
/priority important-longterm
/milestone v1.22

[k8s-triage-robot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[spiffxp]

/remove-lifecycle stale
/priority backlog
/milestone v1.23

[spiffxp]

/remove-priority important-longterm

[spiffxp]

/remove-priority backlog
/priority awaiting-more-evidence
/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[ameukam]

/remove-lifecycle stale
/lifecycle frozen

[ameukam]

We no longer need to do this. GCR is about to be shutdown https://cloud.google.com/container-registry/docs/deprecations/container-registry-deprecation

See: #1343 for GCR to AR migration

cc @BenTheElder

/close

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

We no longer need to do this. GCR is about to be shutdown https://cloud.google.com/container-registry/docs/deprecations/container-registry-deprecation

See: #1343 for GCR to AR migration

cc @BenTheElder

/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.