Proposal: Evaluate silo-operator and add it to README.md to allow k8s users to discover it

[chalukyaj]

Is your feature request related to a problem? Please describe.
This is only a proposal for my operator fork to be evaluated and considered for inclusion as an additional resource in the pgsty/minio README.md
First of all, thank you maintaining this fork of minio, over the last week I've tried to use several object storage alternatives to minio, and only rustfs and seeweedfs came close or outperformed it, but not with their own issues like erratic memory spikes

So to discover that that the community maintained version not only exists, but has had a recent release which outperforms the last published minio image was a delight. But that got me thinking that the minio-operator would have similar issues, and I couldn't find a fork which would work, so ended up creating my own at https://gitlab.com/chalukyaj/pgsty-silo-operator/-/tree/main

I've released the stable version at https://gitlab.com/chalukyaj/pgsty-silo-operator/-/releases/v7.2.0 and it resolves several CVEs in the packages and existing code along with upgrading the go version and an automated ci to publish and host the images (operator and sidecar) and it's helm charts (operator and tenant) while making the tenant use the pgsty/minio image by default pinned to last verified release tag

Also I am using the prefix pgsty in my repo to indicate the image the tenant will be using, and would like to see if the current repo maintainer would want me to rename it to something else.

Describe the solution you'd like
If the release or the repo itself can be linked in the README.md it would get more attention from folks familiar with your repo who might have a similar use case of running minio inside Kubernetes
And it might even get more eyes at the code itself to identify any bug or security vulnerability I might have missed.

Describe alternatives you've considered
NA

Additional context

NA

[chalukyaj]

Will be closing this as I'll be moving this to a different gitlab namespace which will only have open source projects. Will reopen once the migration is done

[dekonnection]

Hi,

I'm really interested in a revival of the minio-operator for Silo, do you have any news about silo-operator ?
Did your plans changed about releasing or maintaining it ?

I'm pretty sure it would interest a lot of people in need of object storage on k8s.

Thanks !

[chalukyaj]

Hi @dekonnection,
Sorry, it had slipped my mind to provide the link to the updated operator repo. I had to move all the open source projects to a different subgroup and I had closed the issue to prevent the outdated link from being linked accidentally

This is the current repo path: pgsty-silo-operator
I've made some changes in the dockerfile and the release process since the last time, and I've also started publishing both operator and sidecar images for linux/amd64 and linux/arm64 platforms and also incorporated vulnerability check in the dockerfile

You can take a look at the builds at https://gitlab.com/open-source-open-colab/pgsty-silo-operator/-/pipelines

Also, I've renamed the repo to be more indicative of the fact that it uses pgsty/silo images instead of minio/minio images by using the keywords pgsty & silo in the name. Do let me know if that's a conflict and you'd want me to rename it to something else.
Any changes/suggestions in the code or release process is welcome.