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

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

Migrate triage dashboard to wg-k8s-infra · Issue #1305 · kubernetes/k8s.io · GitHub

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

Triage is made up of a few components

• periodic jobs run via prow.k8s.io - these should be changed to run on k8s-infra-prow-build
• data files stored in gs://k8s-gubernator/triage - these should be migrated to a new k8s-infra owned GCS bucket
• a static site hosted in gs://k8s-gubernator/triage - ditto
• a http://go.k8s.io/triage redirect that points to the static site - this should be updated to point to the new location

Where should we move things to? My suggestions:

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

One other wrinkle: visiting https://go.k8s.io/triage redirects to https://storage.googleapis.com/k8s-gubernator/triage/index.html which exposes the bucket. If we change to use a new bucket, we're probably going to break a lot of existing URI's. Ideally we can serve a 301 redirect pointing to the new location. Bonus points if we could mask out the bucket name (eg: have triage.k8s.io be our location)

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