Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/kubernetes/k8s.io/issues/1306 below:

Migrate test-infra metrics to wg-k8s-infra · Issue #1306 · kubernetes/k8s.io · GitHub

Part of migrating away from gcp-project k8s-gubernator: #1308

These queries: https://github.com/kubernetes/test-infra/tree/master/metrics

• prow jobs that run via prow.k8s.io - these should be migrated to run on k8s-infra-prow-build (-trusted?)
• results are stored in gs://k8s-metrics - we should use a k8s-infra owned bucket instead

Proposal for new projects/names

• gcp project: k8s-gubernator -> kubernetes-public
• gcs bucket: gs://k8s-metrics -> k8s-project-metrics

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

• setup new bucket, allow google and community prow to write to it ( infra/gcp/main: add k8s-project-metrics special-case #2442)
• rsync data from old bucket to new bucket
• setup canary job on community prow to write to new bucket ( config/jobs: add metrics-bigquery-canary test-infra#23097)
• confirm bigquery can be queried and bucket can be written
• delete old bucket, rename new bucket to old bucket
• swap/delete canary so "real" job runs on community infra

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4