This message was deleted.

Thanks a lot for the feedback, it’s true that our Github repo doesn’t state anything about the stability state or release plans as of now. This is something we need to improve as we need to set the right expectation for our users

BTW: Why is the repo under aquarist-labs? I thought it is a rancher (resp. now Suse?) project. I would assume that it’s located in their github projects. At first I thought that this was just a fork Repo and it took me a while to realize that this is the canonical source repo for s3gw

s3gw was created by the SUSE Storage team so not from the Rancher “unit” per se.

I see, thanks for the clarification. This also may be something to explain in a sentence in the repos readme, so people know that this is the real repo and not a 3rd party fork 🙂

yep, we have a plan for improving our documentation next year as part of our release cycle/development phase. I will add this to the list 😉

Cool! And thank you all for working on s3gw 🙂

thanks @billions-secretary-56562, stay tune for more news! I’m really excited by the upcoming integration with Longhorn and the release/feature plan for FY24! and of course your feedback will be more than welcomed and appreciated

If you integrate it in longhorn, please make sure that you can still just start the container locally. The options to develop applications that use S3 are limited as it is right now and when you can’t run an S3 service locally, you can’t develop apps for that. And running kubernetes locally just to have S3 is overkill and too much complexity for a simple task.