-
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
Redirect dl.k8s.io traffic to a community-owned GCS bucket instead of kubernetes-release #1569
Comments
(Opened #1857 for dl.k8s.io/ci.) |
I manually initiated a one-time transfer from |
@justaugustus I would still like us to do this before we consider flipping over dl.k8s.io for real I could be convinced to flip over temporarily to get an estimate of the amount of traffic this flips, but we should ultimately be using a similar approach as we do for GCR, with promotion from a staging bucket etc. /assign @saschagrunert @puerco @cpanato @jeremyrickard |
Postponed to v1.28 /milestone v1.28 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
We're still not always redirecting away from the bucket and we have most traffic going to the bucket directly (some of which is just skipping the redirect because users have come to depend on the GCS bucket). We need to: |
/milestone v1.29 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone v1.31 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/milestone v1.32 |
Part of umbrella issues:
Traffic gets to
gs://kubernetes-release
in one of two ways:We discussed the idea of cutting over dl.k8s.io traffic first:
The sketch is something like:
Which project/bucket to use:
How to sync:
gcloud
command, but there is an API and some bindings (ref: https://cloud.google.com/storage-transfer/docs/create-manage-transfer-program#cloud-to-cloud)Seeing the delta in traffic:
My preferences would be:
/assign @thockin
since you were part of the discussion
/assign @justaugustus @hasheddan
For @kubernetes/release-engineering input
/wg k8s-infra
/sig release
/sig testing
/area artifacts
/milestone v1.21
The text was updated successfully, but these errors were encountered: