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
Is your feature request related to a problem? Please describe.
Dockerhub has been continuously reducing their image pull quota, announcing plans a couple of months ago to reduce this to 10 per hour in some cases. While this appears to have been silently put on hold, I think that it's likely that dockerhub will further reduce the rate limit in the future.
Describe the solution you'd like
It'd be great if the project could push to quay.io or another registry, similar to other rabbitmq container images.
Describe alternatives you've considered
Cry when I hit the rate limit
Is your feature request related to a problem? Please describe.
Dockerhub has been continuously reducing their image pull quota, announcing plans a couple of months ago to reduce this to 10 per hour in some cases. While this appears to have been silently put on hold, I think that it's likely that dockerhub will further reduce the rate limit in the future.
Describe the solution you'd like
It'd be great if the project could push to quay.io or another registry, similar to other rabbitmq container images.
Describe alternatives you've considered
Cry when I hit the rate limit
Additional context
It looks like the cluster-operator pushes to quay.io.
The text was updated successfully, but these errors were encountered: