The presentation discusses the joint effort between SIG Release, SIG Infra, and other contributors to enforce the migration of Kubernetes images from GCR to Registery. The goal is to serve images from both GCP and AWS, but the migration required manual interaction from users and bending of policies.
- Introduced Registery as a new front for all Kubernetes images to serve images from both GCP and AWS
- Enforced migration from GCR to Registery due to high risk of not having enough GCP Cloud credits for the year
- Bent policies to allow for faster migration despite the policy requiring at least 12 months for users to migrate away from stable features
- Backwards compatibility was introduced to allow for continued access to GCR
- Manual interaction from users was required for the migration
The presenter mentioned that they had to spend 600k more GCP Cloud credits in 2022 than they initially received from Google for that year. This prompted the need for the migration to Registery and the enforcement of the migration despite the policy requiring at least 12 months for users to migrate away from stable features.