You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should expose CRD configuration fields to allow the user to specify their own S3 object storage parameters, so that the user can choose their own storage provider rather than be restricted to the cryostat-storage fork of SeaweedFS.
Not only might the user have some technical/regulatory requirements to not use cryostat-storage and host the storage themselves, but it's likely that any serious production deployment of Cryostat will have particular storage requirements in need of specific tuning, scaling, etc. to suit.
See also #167 (comment)
Related to #814
We should expose CRD configuration fields to allow the user to specify their own S3 object storage parameters, so that the user can choose their own storage provider rather than be restricted to the cryostat-storage fork of SeaweedFS.
Not only might the user have some technical/regulatory requirements to not use cryostat-storage and host the storage themselves, but it's likely that any serious production deployment of Cryostat will have particular storage requirements in need of specific tuning, scaling, etc. to suit.
Some of the relevant configuration properties can be seen here: https://github.com/cryostatio/cryostat/blob/446f0d730e26eac1a2f83035e4f6845fcef7dfd1/compose/s3-seaweed.yml#L7
The text was updated successfully, but these errors were encountered: