What: Modify our devops CI to, upon building an image, also push to the GitHub registry. If it's not too much trouble, we could also push to the DigitalOcean registry.
Why: Our devops CI currently pushes container images only to Docker Hub. That was not a problem, until Docker Hubs institued a pull rate limit: https://www.docker.com/blog/revisiting-docker-hub-policies-prioritizing-developer-experience/ The limits shouldn't be a problem for normal updates of a Hubs instance, but when active development is going on, especially on an instance with multiple nodes, it may well happen.
What: Modify our devops CI to, upon building an image, also push to the GitHub registry. If it's not too much trouble, we could also push to the DigitalOcean registry.
Why: Our devops CI currently pushes container images only to Docker Hub. That was not a problem, until Docker Hubs institued a pull rate limit: https://www.docker.com/blog/revisiting-docker-hub-policies-prioritizing-developer-experience/ The limits shouldn't be a problem for normal updates of a Hubs instance, but when active development is going on, especially on an instance with multiple nodes, it may well happen.