-
Notifications
You must be signed in to change notification settings - Fork 689
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
fix: migrate from k8s.gcr.io to registry.k8s.io #5166
Conversation
Signed-off-by: Waleed Malik <[email protected]>
Hi @ahmedwaleedmalik! Welcome to our community and thank you for opening your first Pull Request. Someone will review it soon. Thank you for committing to making Contour better. You can also join us on our mailing list and in our channel in the Kubernetes Slack Workspace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a generated file pulled from https://github.com/kubernetes-sigs/gateway-api so once that releases a new version, this will be updated accordingly
If I were you, I wouldn't really wait for their release to make this switch. But I'd leave that up to you. As long as you are not affected by https://kubernetes.io/blog/2023/03/10/image-registry-redirect/ |
We can't just update this file statically because it will cause our codegen CI to fail. However, I'm thinking it might be a good idea to add a temporary step to https://github.com/projectcontour/contour/blob/main/Makefile#L253-L259 to replace the old registry with the new. I'm not concerned about it on |
yeah that sounds like a good idea! |
@ahmedwaleedmalik I've opened #5175 for this and added you as a co-author, will be closing this one out. Thanks! |
Kubernetes is migrating its image registry from k8s.gcr.io to registry.k8s.io.
Part of kubernetes/k8s.io#4780