Unconditional rulerConfig in values.yaml

[Tostaza]

Is your feature request related to a problem? Please describe.

I've been recently trying to install loki and configure it to store logs in an external minio instance. I'm not using the ruler component since I only want to store chunks in one bucket. Even though I have disabled the ruler in my values.yaml, the config section does not check it and unconditionally includes a rulerConfiguration. Since I have not provided a bucket for the ruler, the loki-backend pod fails and enters CrashLoopBackOff state

Describe the solution you'd like
Add an if statement in the default values.yaml to include loki.rulerConfig only if ruler.enabled: true

Describe alternatives you've considered
If anybody has the same problem, some temporal fixes would be:

• Add the if statement in the provided custom values. This means you should copy all the config section in your values.yaml.
• You can also specify an existing bucket for the ruler (e.g the same as for chunks). This will avoid the loki-backend failing. Notice that even if its specified, the ruler will not store info since its disabled

loki/production/helm/loki/values.yaml

Line 208 in f2bff77

{{ include "loki.rulerConfig" . }}

[Tostaza]

A solution is provided here: #15385