Use cloud provider registries for user images instead of quay.io

[yuvipanda]

Description

Right now, we put custom user images on quay.io. We should explore using the registries that are provided by individual cloud providers instead.

Benefit

The main benefit here is performance. For a hub on a given cloud provide, if images are served from the same provider, they will pull faster than images served from quay.io.

#331 should help determine how much of a performance hit this is.

Tasks to complete

• Wait for Support and document pushing to AWS ECR jupyterhub/repo2docker-action#65 needs to land so we can actually support pushing to the cloud native registries.
• Explore how much of an improvement we get by pulling from the cloud native registries, and decide what to do next.

[GeorgianaElena]

@yuvipanda, shouldn't jupyterhub/repo2docker-action#65 be fixed by jupyterhub/repo2docker-action#73?

[GeorgianaElena]

I was experimenting with using the repo2docker action to push images to a private aws ecr registry over here https://github.com/GeorgianaElena/test-repo2docker-action and don't seem to be able to make it work. I'm wondering if it's because I misunderstood things and this isn't yet possible because some important piece of jupyterhub/repo2docker-action#65 is missing?

[sgibson91]

I'm wondering if it's because I misunderstood things and this isn't yet possible because some important piece of jupyterhub/repo2docker-action#65 is missing?

If this is true, I'd look to see what docker/build-push-action is doing behind the scenes, as it does support pushing to multiple registries