Add minio

[chrisburr]

This adds minio to the chart. It's exposed to the host using two node ports which isn't ideal but it probably the nicest thing for development to avoid needing to play with DNS resolution (minio doesn't support running on anything other than /).

[chaen]

Are you sure it doesn't work through ingress ? This problem seems to have been fixed with minio/console#2818

[chrisburr]

Are you sure it doesn't work through ingress ? This problem seems to have been fixed with minio/console#2818

I had tried but I didn't manage and thought I had read that it was only possible for the console and not for the main S3-compatible API endpoint. That said, I'd be very happy to be wrong 😄

[chaen]

I had quite a play with this, and although I managed to make it work with the ingress and some caveats, I think that for the time being, we should indeed stick to the node port for local development.

The reason is that the best way to make it work is to expose extra ports in the ingress (9000 and 9001) for example. And this can be done (see for example https://gitlab.cern.ch/lhcb-dirac/diracchart/-/blob/master/charts/dirac/values.yaml#L200-231)
However, when running locally with kind, we do not manage the ingress with helm, so you can't update it with helm. So it probably isn't worth the trouble.
We may however keep that solution in mind for production configuration

[chrisburr]

I think the way to go is with node port for development and SNI for production.