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

Feature Request: Object Storage (S3) #102

Closed
benedikt-bartscher opened this issue Mar 18, 2023 · 3 comments
Closed

Feature Request: Object Storage (S3) #102

benedikt-bartscher opened this issue Mar 18, 2023 · 3 comments

Comments

@benedikt-bartscher
Copy link

It would be great if flexo could store packages in object storage, for example s3.
This would further reduce external traffic in clusterized deployments and make it easy to deploy flexo HA.

@nroi
Copy link
Owner

nroi commented Mar 20, 2023

Can you explain in a bit more detail how you use flexo? I would have expected most if not all users to deploy flexo inside their own four walls in a LAN reachable by a desktop or laptop client. But when you talk about S3, I guess you deploy flexo at AWS or some other cloud provider?

@benedikt-bartscher
Copy link
Author

Thanks for your response. I have multiple flexo deployments with helm+k8. Some of them are on-site (local) and some of them in AWS. However every flexo instance is deployed with k8 and 3 pods. Currently these pods use local storage which is not optimal. I would only like to fetch every package 1x from the upstream mirrors to reduce external traffic and increase speed.

@nroi
Copy link
Owner

nroi commented Mar 25, 2023

I see.

Adding S3 as an additional storage provider would considerably increase the complexity of flexo, since there are some challenges to be addressed. For example, S3 does not support appending data to an existing object. Writing test cases would also become more difficult, because you would have to mock an external provider if you want your tests to run without external dependencies. I'm sure that these are all problems that can be solved, but only with considerable additional complexity.

My assumption is that deploying flexo in an HA environment is more of a niche use-case, hence there are many other issues that provide more benefit for less effort. So this is not on my roadmap in the near future.

Anyone who's interested in this feature: Feel free to comment and argue why you would find this useful, I'm always interested to hear how people use flexo. But since is not on my roadmap at the moment, I'm closing this for now.

@nroi nroi closed this as completed Mar 25, 2023
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

No branches or pull requests

2 participants