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

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

Migrate away from google.com gcp project kubernetes-ci-images · Issue #1460 · kubernetes/k8s.io · GitHub

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 of gs://kubernetes-release-dev
• gcr.io/k8s-staging-ci-images instead of gcr.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 to gcr.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 a ci/foo version
  • may impact cluster-api and its implementations
  • may impact kinder

I'm starting this as an umbrella issue here. It may require a KEP, or it may be better homed in kubernetes/kubeadm.

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