Scalable Loki depends on Minio Operator when not using creds

Installing the scalable Loki HelmRelease forces a dependency on minio-operator, see here. At CMS we are storing logs in AWS S3 and access the buckets using IRSA, and we do not use AWS access key/secret creds. So, we'd like the option to use scalable Loki without Minio

assigned to @gedd.johnson

We can look into tightening loosening up the conditionals here for sure... @ryan.j.garcia would it be sufficient to change the conditional to just {{- if not (and .endpoint .bucketNames) }} (just looking for endpoint and bucketnames)?

We also should adjust the top conditional since its vulnerable to edge cases right now if a lot of things are disabled - https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/chart/templates/logging/loki/loki-helmrelease.yaml#L40

Yeah would be worth doing that. If the goal is to use an IAM/Instance Profile it is not possible currently for Loki/Tempo so credentials are required. Pulling it in as low priority for the XForce Team.

The monolithic Loki deployment does allow us to use an IAM/Instance Profile to access S3. To get around the Minio Operator dependency I'm setting my values as:

loki:
  enabled: true
  # need this block to ensure minio is not a dependency
  objectStorage:
    endpoint: whatever
    accessKey: whatever
    accessSecret: whatever
    bucketNames: whatever
...

And we are able to succesfully put Loki logs into S3

added kindenhancement loki priority6 teamXForce labels

set weight to 2

added to epic &143 (closed)

changed iteration to Big Bang Iterations Jul 26, 2022 - Aug 8, 2022

changed the description

mentioned in merge request !1908 (merged)

added statusdoing label

assigned to @ryan.j.garcia and unassigned @gedd.johnson

set weight to 0

added statusreview label and removed statusdoing label

removed iteration Big Bang Iterations Jul 26, 2022 - Aug 8, 2022

changed iteration to Big Bang Iterations Aug 9, 2022 - Aug 22, 2022

closed with merge request !1908 (merged)

mentioned in commit e254cf6d

removed statusreview label

changed milestone to %1.41.0