-
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
Deprecate and migrate away from gs://kubernetes-release-dev and gcr.io/kubernetes-ci-images #2318
Comments
Went on a bit of a spree today and opened the following:
Where possible I tried to converge toward dl.k8.io instead of a simple s/kubernetes-release-dev/k8s-release-dev, since this is somewhat of a dry-run for the work to migrate |
The only time a kubernetes GCS bucket name should be showing up in a hardcoded URI is if gsutil is being used (e.g. gsutil cp gs://foo/bar .) Otherwise, for tools like curl or wget, dl.k8s.io is much nicer for us as a project, since we can transparently change where that redirects to without having to change code everywhere These changes will mean very few changes will be necessary to accommodate a gs://kubernetes-release -> gs://k8s-release migration equivalent of the CI migration we're going through right now These changes also address the gs://kubernetes-release-dev references currently used by this repo (ref: kubernetes/k8s.io#2318)
Two more PRs opened / merged:
Need to do another pass and make sure documentation is wrapped up |
I missed that the release-branch cut caused v1.23 builds to start getting pushed: |
This should take care of the last of the non-necessary/historically-archived kubernetes-relesase-dev references: |
/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. |
Part of umbrella issue to migrate the kubernetes project away from use of GCP project google-containers: #1571
This issue covers the deprecation of and migration away from two google.com assets:
gs://kubernetes-release-dev
living in GCP projectgoogle-containers
, in favor of the community-owned GCS bucketgs://k8s-release-dev
living in GCP projectk8s-release
gcr.io/kubernetes-ci-images
, in favor of the community-owned GCR repogcr.io/k8s-staging-ci-images
Step 1: Set and announce deprecation window
The first part is setting and announcing a deprecation window for CI artifacts placed in gs://kubernetes-release-dev, and their companion images in gcr.io/kubernetes-ci-images e.g.
gs://k8s-release-dev/ci
andgs://kubernetes-release-dev/ci
simultaneouslygcr.io/k8s-staging-ci-images
instead ofgcr.io/kubernetes-ci-images
gs://kubernetes-release-dev/ci-cross
gs://kubernetes-release-dev
andgcr.io/kubernetes-ci-images
gs://kubernetes-release-dev
andgcr.io/kubernetes-ci-images
completely once older CI jobs have aged out according to the kubernetes version support policy, or when we see no remaining traffic togs://kubernetes-release-dev
for a period of N weeksStep 2: Setup community-owned alternatives, and use them for release-blocking / merge-blocking CI
This is a rough breakdown of the work necessary to complete the heavy lifting before we can shard out work to all repos across the project
gs://kubernetes-release-dev
togs://k8s-release-dev
- dl.k8s.io: Redirect CI URIs to Kubernetes Community infra #1857 (@justaugustus), k8s.io: fix dl.k8s.io/ci redirect #2292 (@spiffxp)gs://kubernetes-release-dev/kops/ci
- remove references to kubernetes-release-dev kops#11997 (@spiffxp)k8s-release-dev
instead ofkubernetes-release-dev
- use gs://k8s-release-dev for kubernetes CI builds test-infra#22840 (@spiffxp)k8s-release-dev
instead ofkubernetes-release-dev
- bash: use k8s-release-dev for CI builds release#2158 (@spiffxp)Step 3: Ensure no references to kubernetes-release-dev within project
The next part of this is ensuring there are no remaining references to
kubernetes-release-dev
outside ofvendor/
directories (except those necessary for theci-kubernetes-build-.*deprecated.*
jobs to satisfy the deprecation window)k8s-release-dev
instead ofkubernetes-release-dev
This is pretty easily verifiable (with human inspection of results) using https://cs.k8s.io
Step 4: Ensure no references to kubernetes-ci-images within project
k8s-staging-ci-images
instead ofkubernetes-ci-images
Step 5: Complete deprecation
Related issues
/wg k8s-infra
/sig testing
/area prow
FYI @kubernetes/sig-testing-leads
/sig release
/area artifacts
/area release-eng
FYI @kubernetes/release-engineering
/kind cleanup
/kind deprecation
/priority important-soon
/milestone v1.22
/assign
The text was updated successfully, but these errors were encountered: