You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some people are hitting the dockerhub's rate limitation. This is more severe for people who are pulling images behind company firewall because they are more likely to be seen as one entity. We should pull images from Quay.io because it does not have rate limitation.
Describe the Solution You Would Like to See
We should update the any tests that are pulling from docker.io by using an equivalent image from quay.io
For example, in run-e2e-kind.sh we should update these images kicbase/echo-server:1.0 and k8s.gcr.io/busybox:latest
Hey @tedhtchang, I got it! I was able to push up the following images to quay.io, and they're multi-arch images (amd64 and arm64) so they will work on both Intel and Mac servers.
Name of Feature or Improvement
Change registry to Quay.io
Description of Problem the Feature Should Solve
Some people are hitting the dockerhub's rate limitation. This is more severe for people who are pulling images behind company firewall because they are more likely to be seen as one entity. We should pull images from Quay.io because it does not have rate limitation.
Describe the Solution You Would Like to See
We should update the any tests that are pulling from docker.io by using an equivalent image from quay.io
For example, in run-e2e-kind.sh we should update these images kicbase/echo-server:1.0 and k8s.gcr.io/busybox:latest
Additional Context
conversation
https://project-codeflare.slack.com/archives/C04L7QH4Q84/p1697050826438579
/cc @asm582
The text was updated successfully, but these errors were encountered: