Closed
Description
Part of umbrella issue to migrate away from google.com gcp projects: #1469
Part of umbrella to migrate kubernetes e2e test images/registries to community-owned infrastructure: #1458
Pulling this out of kubernetes/test-infra#19483 which covered running ci-kubernetes-build
on community-owned infrastructure
The community-owned job now writes artifacts to:
gs://k8s-release-dev
instead ofgs://kubernetes-release-dev
gcr.io/k8s-staging-ci-images
instead ofgcr.io/kubernetes-ci-images
We need to migrate away from gcr.io/kubernetes-ci-images
, which will involve:
- announce deprecation of
gcr.io/kubernetes-ci-images
- migrating jobs/subprojects to use
gcr.io/k8s-staging-ci-images
instead
During the deprecation window, we will need to either:
- continue running a google.com job that publishes to
gcr.io/kubernetes-ci-images
- setup a job that syncs from
gcr.io/k8s-staging-ci-images
togcr.io/kubernetes-ci-images
Once the window has passed, we can:
- delete the old job
- delete the old project
Potential impact (ref: kubernetes/test-infra#19483 (comment))
- anyone downstream who consumes
gcr.io/kubernetes-ci-images
- clusters using
kubeadm
without a custom image repository and with aci/foo
version- may impact
cluster-api
and its implementations - may impact
kinder
- may impact
I'm starting this as an umbrella issue here. It may require a KEP, or it may be better homed in kubernetes/kubeadm.
Metadata
Metadata
Labels
Issues or PRs related to the hosting of release artifacts for subprojectsIssues or PRs related to the Release Engineering subprojectMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.Categorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Testing.