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.

Sign up for GitHub

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

Jump to bottom

Switch from k8s.gcr.io to registry.k8s.io #1734

Closed
z0rc opened this issue Jun 7, 2022 · 5 comments · Fixed by #1758
Closed

Switch from k8s.gcr.io to registry.k8s.io #1734

z0rc opened this issue Jun 7, 2022 · 5 comments · Fixed by #1758
Labels
area/k8s-upstream lifecycle/active Actively being worked on misc/good first issue

Comments

@z0rc
Copy link

z0rc commented Jun 7, 2022

Describe the solution you'd like
Kubernetes project is working on switching to new registry by 1.25 release. See kubernetes/k8s.io#1834 and kubernetes/kubernetes#109938. Sonobuoy should follow this change eventually. There are multiple places in code that reference k8s.gcr.io now.

Anything else you would like to add:
Announcement at https://groups.google.com/g/kubernetes-sig-testing/c/U7b_im9vRrM/m/7qywJeUTBQAJ.
@johnSchnake
Copy link
Contributor

Thanks! 👍

We will make sure to track this.

@johnSchnake
Copy link
Contributor

We have come to the point where we have a proxy in front of k8s.gcr.io named registry.k8s.io...

I wonder if we really need to do anything if they've already put a proxy in front to redirect the important traffic. Investigating. There are lots of threads to read so if someone knows the answer, feel free to point me to it directly.

@johnSchnake johnSchnake added the lifecycle/active Actively being worked on label Jun 29, 2022
@z0rc
Copy link
Author

z0rc commented Jun 30, 2022

AFAIK proxy setup will be like this for transition period, but it isn't clear how long this period will last. Nonetheless Kubernetes 1.25 is expected to switch to new registry by default, so I guess old registry will be available for 1-2 releases after 1.25 until it's completely deprecated.

@johnSchnake
Copy link
Contributor

johnSchnake commented Jul 1, 2022 •
edited
Loading

Trying to just tinker to be more confident with the change and got this:

docker pull registry.k8s.gcr.io/conformance:v1.23.3
Error response from daemon: Get "https://registry.k8s.gcr.io/v2/": x509: certificate is valid for *.googlecode.com, *.cloud.google.com, *.code.google.com, *.codespot.com, *.developers.google.com, *.clients6.googlesource.com, *.googlesource.com, googlesource.com, *.u.googlecode.com, gcr.io, *.gcr.io, pkg.dev, *.pkg.dev, googlecode.com, not registry.k8s.gcr.io

Same thing when I tried skopeo list-tags ...

Investigating.

Investigation complete after 2m. s/registry.k8s.gcr.io/registry.k8s.io

@johnSchnake
Copy link
Contributor

Tried to just confirm that all the images we expect (all the conformance images) are available in both locations; confirmed via skopeo list tags... to each registry and diff'd them. No differences.

Making change 👍

@johnSchnake johnSchnake mentioned this issue Jul 1, 2022
Merged
johnSchnake added a commit that referenced this issue Jul 1, 2022
@johnSchnake
Move to registry.k8s.io
dd9992f 
The community is trying to reduce traffic to k8s.gcr.io
and is asking that people move to registry.k8s.io whenever
possible. Currently there is a proxy that will redirect you
so it won't break if we dont updata right away, but since
the change is so close, it is advised that we move now.

Fixes #1734

Signed-off-by: John Schnake <jschnake@vmware.com>
@emosbaugh emosbaugh mentioned this issue Jul 22, 2022
Merged
@eliyamlevy eliyamlevy mentioned this issue Aug 5, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/k8s-upstream lifecycle/active Actively being worked on misc/good first issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Move to registry.k8s.io
2 participants
@z0rc @johnSchnake