Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Container Registry (GCR) to Artifact Registry (AR) migration outage #19541

Closed
spowelljr opened this issue Aug 29, 2024 · 0 comments
Closed

Comments

@spowelljr
Copy link
Member

We were previously on GCR, which is getting shut down (link), so on August 27th I started the migration process to AR. I routed 100% of the traffic to AR and everything seemed fine.

Then on the 28th I noticed that our registry addon tests started to fail (link) since the migration, so I routed 99% of traffic back to GCR and 1% to AR. However, it seems that traffic routed to GCR results in pull errors due to unauthorized errors.

On the 29th I saw reports from users that they were experiencing pull issues and saw the same on our CI, I routed 100% of traffic back to AR. All image pull issues should now be resolved. I'll follow up internally to figure out what happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant