-
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
Migrate test-infra metrics to wg-k8s-infra #1306
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/assign @MushuEE |
/milestone v1.21 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
/milestone v1.22 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
|
Working on using the new infra via a canary job:
|
No auto sync planned regularly? |
If I can get away with moving the bucket vs. having to migrate all links to the new bucket, no, no periodic sync |
https://testgrid.k8s.io/wg-k8s-infra-canaries#metrics-bigquery-canary - currently failing
Hm, ok, but when I run locally with my google.com account or my personal account
I ended up changing this job from a bootstrap job to decorated, I wonder if it needs to be updated to work with workload identity |
kubernetes/test-infra#23102 - workload identity is my best guess for now |
Turns out it was adding 'm sure there's a much more locked down set of permissions we could try, such that the service account doesn't accidentally create datasets in k8s-infra-prow-build-trusted, but I think this is good enough for now. |
Did the dance to empty out the old bucket, remove it, create a new bucket with the same name in the new GCP org/project, and sync contents back
|
Alright! The bucket lives in kubernetes.io, the latest job ran in kubernetes.io, and everything works:
Cleaning up:
|
|
/miletone v1.22 |
#2454 has merged Calling this done! /close |
@spiffxp: Closing this issue. In response to this:
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. |
/milestone v1.22 |
Part of migrating away from gcp-project k8s-gubernator: #1308
These queries: https://github.com/kubernetes/test-infra/tree/master/metrics
Proposal for new projects/names
I know of at least some people who link directly to the in-bucket json, eg: http://storage.googleapis.com/k8s-metrics/flakes-latest.json. It would be helpful if we could instead serve 301 redirects to the new location of these files
EDIT(spiffxp):
The plan
The text was updated successfully, but these errors were encountered: