-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infra/gcp/main: add k8s-project-metrics special-case #2442
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ea842a3
to
8d092ef
Compare
/cc @ameukam @dims |
8d092ef
to
9720d00
Compare
k8s-metrics is a low-traffic GCS bucket for the project, setup permissions to trial moving it from one org to the other. The steps for this process are going to look something like: - allow google.com prow to write to the new bucket - allow k8s-infra-prow-build-trusted to write to the new bucket - allow humans to own the new bucket - sync contents from old bucket to new bucket - setup canary job on k8s-infra-prow-build-trusted that writes to the new bucket to confirm permissions are correct for executing bigquery queries that use the k8s-gubernator:builds dataset and writing to the new bucket - remove canary job / move old job to k8s-infra-prow-build-trusted - delete old bucket - rename new bucket to old bucket
9720d00
to
adbd4e2
Compare
/lgtm |
/lgtm |
/hold cancel |
|
Related:
k8s-metrics is a low-traffic GCS bucket for the project, setup permissions to trial moving it from one org to the other. The steps for this process are going to look something like:
bucket to confirm permissions are correct for:
If the rename fails, we'll use the new bucket name and look into a redirect from old files.