k8s.gcr.io VDF (Vanity Domain Flip): Move official container images to K8s Infra

[jbeda]

Google Infra --> K8s Infra tasks (ordered by priority):

• Ensure that k8s-artifacts-prod GCR is a superset of google-containers (aka backfiling; this has already been done and is easy to check before VDF happens)
• Fix auditor's ability to handle child images in fat manifests (issue)
• Optimize backup mechanism (issue)
• Add CLI command to make editing the promoter manifests easier (issue)
• Auditor alerts --> <somewhere>

Release Engineering

• (releng: Add new projects for staging/releasing Kubernetes k8s.io#624) Create k8s-staging-kubernetes GCP project (prod staging project)
• (backfill images from google-containers k8s.io#623) Backfill prod k8s.gcr.io images
• Figure out image promotion for staging
  • (releng: Use a temp namespace for k8s-staging-kubernetes promotion k8s.io#645) Configure k8s-staging-kubernetes promoter-manifest to point to test prod namespace
  • (Grant kubernetes-release-test GCB write on k8s-staging-kubernetes GCR k8s.io#673, Empower old release GCB to push to staging k8s.io#675) Grant kubernetes-release-test GCB write on k8s-staging-kubernetes GCR
  • ([VDF] anago: Publish container images on K8s Infra (k8s-staging-kubernetes) #1199) Publish container images on K8s Infra (k8s-staging-kubernetes)
  • Add CLI command to dump and merge an image manifest for promotion - [Feature request] Add CLI command to dump and merge an image manifest for promotion kubernetes-sigs/promo-tools#190

---

Original note from @jbeda:

We should not be using a Google only repo for official k8s builds.

[ixdy]

Yep, this is something that @timstclair and I are looking into.

[timstclair]

We're expecting to have a proposal out in the next week or two that will address this.

[zmerlynn]

Please include me. We have internal infrastructure that handles the replication of google-containers to non-US regions.

[luxas]

Please include me as well, I have been thinking about this for some time as well, but haven't just had the time to focus fully on trying to make a change here (not that I have the permissions to do so either but 😄)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[david-mcmahon]

cc @javier-b-perez

[luxas]

Progress: kubernetes/kubernetes#54174

/remove-lifecycle stale

cc @thockin @ixdy

What are the next steps here?
To start moving over images to a specific Kubernetes suborg gradually and/or updating refs in all other repos as well?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale