Open rjferguson21 opened 5 months ago
I think this would make sense to add as optional. It might also make a lot of sense to switch minio to optional at the same time - in a lot of dev/CI environments it's probably just extra bloat that isn't used (ex: most uds-core single pkg tests)?
Minio is definitely extra bloat. The postgres operator would be as well. The only issue i see with this approach though is that if either are included in this package specifically it cant be done in a way that properly integrates with istio, which makes testing against the minio or postgres not representative of what it would be in a real environment. If they were being exposed public to the cluster it would mimic and external resource, but not sure what the desire is for that.
For testing components that require a Postgres database it would be nice to just include the operator as an optional component