Bug: Mimir doesn't not pick config from values.yaml name: mimir-distributed version: "5.8.0" #13597
Unanswered
SergiiOliinyk
asked this question in
Help and support
Replies: 1 comment 1 reply
-
|
Converting to a discussion because this doesn't seem like a bug in Mimir. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What is the bug?
We have values.yaml in Helm chart
Argo CD deploys everything, but the config file is ignored, and Mimir uses the default one. See a sample how to reproduce below and default config generated
How to reproduce it?
Use Helm chart
dependencies:
version: "5.8.0" # You can upgrade anytime
repository: "https://grafana.github.io/helm-charts"
Put the following config in dev-values.yaml and deploy
dev-values.yaml
What did you think would happen?
helm template mimir . -f dev-values.yaml > rendered.yaml or using Argo CD
Default config instead of modified based on config above rendered.yaml
What was your environment?
Helm, Kubernetes, Argo CD
Any additional context to share?
rendered.yaml
Beta Was this translation helpful? Give feedback.
All reactions