Skip to content

Publish to quay.io or another container registry #978

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

Open
solidDoWant opened this issue Apr 17, 2025 · 0 comments · May be fixed by #980
Open

Publish to quay.io or another container registry #978

solidDoWant opened this issue Apr 17, 2025 · 0 comments · May be fixed by #980

Comments

@solidDoWant
Copy link

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.

@MirahImage MirahImage linked a pull request Apr 23, 2025 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant