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 project google-containers
, in favor of the community-owned GCS bucket gs://k8s-release-dev
living in GCP project k8s-release
gcr.io/kubernetes-ci-images
, in favor of the community-owned GCR repo gcr.io/k8s-staging-ci-images
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
and gs://kubernetes-release-dev/ci
simultaneouslygcr.io/k8s-staging-ci-images
instead of gcr.io/kubernetes-ci-images
gs://kubernetes-release-dev/ci-cross
gs://kubernetes-release-dev
and gcr.io/kubernetes-ci-images
gs://kubernetes-release-dev
and gcr.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 to gs://kubernetes-release-dev
for a period of N weeksThis 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
to gs://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 of kubernetes-release-dev
- use gs://k8s-release-dev for kubernetes CI builds test-infra#22840 (@spiffxp)k8s-release-dev
instead of kubernetes-release-dev
- bash: use k8s-release-dev for CI builds release#2158 (@spiffxp)The next part of this is ensuring there are no remaining references to kubernetes-release-dev
outside of vendor/
directories (except those necessary for the ci-kubernetes-build-.*deprecated.*
jobs to satisfy the deprecation window)
k8s-release-dev
instead of kubernetes-release-dev
This is pretty easily verifiable (with human inspection of results) using https://cs.k8s.io
$ curl -s -X POST \
-F "q=kubernetes-release-dev" \
-F "repos=*" \
-F "excludeFiles=vendor/" \
"https://cs.k8s.io/api/v1/search" \
| jq -r '.Results | keys | .[]' \
| sort \
| sed -e 's/^/- [ ] /g'
k8s-staging-ci-images
instead of kubernetes-ci-images
$ curl -s -X POST \
> -F "q=kubernetes-ci-images" \
> -F "repos=*" \
> -F "excludeFiles=vendor/" \
> "https://cs.k8s.io/api/v1/search" \
> | jq -r '.Results | keys | .[]' \
> | sort \
> | sed -e 's/^/- [ ] /g'
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
You can’t perform that action at this time.
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