Loki Storage Logic needs exception for MinIO

Currently, the loki storage configuration refers s3 if loki deployment type != Monolith even if s3 isn't the intended endpoint (i.e. not filled), causing an error. This needs to be fixed. See current logic https://repo1.dso.mil/big-bang/bigbang/-/blob/master/chart/templates/loki/values.yaml?ref_type=heads#L81

added loki teamObservability labels

mentioned in merge request !5809 (closed)

changed the description

assigned to @kliu

added triage-kind label

added triage-priority label

assigned to @bjacksonfv

set weight to 3

mentioned in merge request !5818 (closed)

Conversation with @michaelmartin, when loki strategy is scalable, aws s3 should be used instead of MinIO, closing this issue.

closed

changed weight to 2 from 3

Since MinIO is supported in production and is intended to be dev testing when loki strategy is scalable, when users are using strategy == scalable they should be using the aws s3 (or bring their own object storage). The MR to enable minio in the maintenance_development.md when testing loki has been documented in this mr- big-bang/product/packages/loki!310 (merged)

mentioned in merge request big-bang/product/packages/loki!310 (merged)

changed iteration to Big Bang Iterations Feb 18, 2025 - Mar 3, 2025