Skip to content
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

Open
A-Ashiq opened this issue Mar 13, 2024 · 4 comments
Open

Publish unleash-server image to the AWS public ECR gallaery #6530

A-Ashiq opened this issue Mar 13, 2024 · 4 comments

Comments

@A-Ashiq
Copy link

A-Ashiq commented Mar 13, 2024

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 and unleash-server. But the AWS public ECR gallery only contains just the 2 images of unleash-edge and unleash-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 way unleash-edge and unleash-proxy are already being done for the public AWS ECR gallery

@A-Ashiq
Copy link
Author

A-Ashiq commented Mar 13, 2024

Screenshot 2024-03-13 at 10 17 38

@thomasheartman
Copy link
Contributor

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.

@A-Ashiq
Copy link
Author

A-Ashiq commented Mar 14, 2024

Hey @thomasheartman thanks for getting back to me.
That is not a problem, I thought that would be the case 😄

Send my thanks to your team for all the hard work that has gone into this!

Copy link

stale bot commented Apr 13, 2024

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.

@stale stale bot added the stale label Apr 13, 2024
@stale stale bot removed the stale label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: For later
Development

No branches or pull requests

2 participants