registry.k8s.io Production Readiness/Timelines

[upodroid]

registry.k8s.io is the community owned and managed image registry for the Kubernetes project and it has been running for sometime.

We need to do the following for it to be ready for production and wider rollout:

1. Move from k8s.gcr.io to registry.k8s.io kubernetes#109938
2. We need to manage the configuration of oci-proxy via Terraform and GitOps.
3. Upgrade oci-proxy to serve images from AWS. @BobyMCbobs

   cy@cloudshell:~ (k8s-infra-oci-proxy-prod)$ gcloud run services list
   ✔
   SERVICE: k8s-infra-oci-proxy-prod-asia-east1
   REGION: asia-east1
   URL: REDACTED
   LAST DEPLOYED BY: [email protected]
   LAST DEPLOYED AT: 2022-03-28T07:58:25.682843Z
   

4. Google Container Registry to Artifact Registry Migration Timelines #3976 Configure oci-proxy to serve images from Artifact Registry. From sig-k8s-infra's perspective, AR has all the images from GCR and is autosynced from GCR every 2 hours. Direct Promotion is still being worked on and not a hard requirement for image serving.
5. Work with Google on redirecting k8s.gcr.io to registry.k8s.io. @BenTheElder
6. Cut 0.0.2 release registry.k8s.io#97
7. Write a blog post on kubernetes.io, send emails to mailing list, etc

Optional Activities:

• Rename this repo to registry.k8s.io registry.k8s.io#94

Tentative Prod Launch Date: 01/10/2022 I'm looking to get all of this resolved by this date excluding the k8s.gcr.io redirect

@ameukam @dims

/sig k8s-infra
/area artifacts

[BobyMCbobs]

Putting step two into it's own issue to track it
#4123

[BobyMCbobs]

registry.k8s.io's code was enabled for S3 serving
kubernetes/registry.k8s.io#82
i'm unsure if production has yet been deployed

cc @BenTheElder @ameukam

[ameukam]

I'm not sure about the intent of the issue but we went in production with the release of 1.25.
Only Step 5 need some coordination since we don't have clear informations about when It's gonna be done

[upodroid]

I'm not sure about the intent of the issue but we went in production with the release of 1.25.

I see it as more of a soft launch. We are missing everything I listed above that need to be sorted out very soon. prod isn't even serving anything from AWS yet.

[BenTheElder]

We're serving from S3 and we're redirecting a small portion of k8s.gcr.io to this with no issues
/close

[k8s-ci-robot]

@BenTheElder: Closing this issue.

In response to this:

We're serving from S3 and we're redirecting a small portion of k8s.gcr.io to this with no issues
/close

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.