-
-
Notifications
You must be signed in to change notification settings - Fork 740
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
Publish unleash-server image to the AWS public ECR gallaery #6530
Comments
Thanks for the feature request! We've noted it down and added it to our backlog. This isn't an urgent task, so we can't give you a clear timeline on it. |
Hey @thomasheartman thanks for getting back to me. Send my thanks to your team for all the hard work that has gone into this! |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Describe the feature request
Publish and sync the latest updates for the
unleash-server
docker image to the AWS public ECR gallery.Background
Currently this image is being published at Docker Hub. Note that the Docker Hub repo contains more images including
unleash-edge
,unleash-proxy
andunleash-server
. But the AWS public ECR gallery only contains just the 2 images ofunleash-edge
andunleash-proxy
.I am currently deploying unleash self hosted into my stack. The workload will be ran as an AWS ECS task, which integrates slightly better with pulling the image from the public AWS ECR gallery as opposed to Docker Hub. I am creating a pull through image repository cache which will sync images from the upstream repo. This allows us to keep images nearby and also scan them in our own private repos.
Note that it is possible to simply pull the image from Docker Hub. The ECS integration simply requires a couple of extra authentication steps with Docker Hub.
For my particular use case, stakeholders are also much more comfortable with the idea of depending on images which are within the AWS ecosystem i.e. the public ECR gallery as opposed to Docker hub.
Solution suggestions
Add the
unleash-server
image and sync updates in the same wayunleash-edge
andunleash-proxy
are already being done for the public AWS ECR galleryThe text was updated successfully, but these errors were encountered: