-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm: loki-canary test pod gets rendered even when tests are disabled #12765
Labels
Comments
Correction: It is not getting deployed unless I run My values.yaml: deploymentMode: SingleBinary
loki:
commonConfig:
replication_factor: 1
storage:
type: filesystem
useTestSchema: true
singleBinary:
replicas: 1
read:
replicas: 0
backend:
replicas: 0
write:
replicas: 0
test:
enabled: false |
I have same issue deploying Loki with ArgoCD |
@elchenberg i just end up setting lokiCanary.enabled: false |
@ilbarone87 Unfortunately that does not work for me because I want to have the Loki Canary. 😕 |
lindhe
added a commit
to lindhe/loki
that referenced
this issue
Dec 10, 2024
Replaces grafana#13180 Fixes grafana#12765 Signed-off-by: Andreas Lindhé <7773090+lindhe@users.noreply.github.com>
lindhe
added a commit
to lindhe/loki
that referenced
this issue
Dec 10, 2024
Replaces grafana#13180 Fixes grafana#12765 Signed-off-by: Andreas Lindhé <7773090+lindhe@users.noreply.github.com>
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I could not find out how to not deploy the loki-canary test pod using the Helm chart v6.4.3 when the loki-canary is enabled but the tests are disabled (
test.enabled=false
).I think the issue was introduced with this change: 79b876b#diff-4f7364c8431077f51149aa596196fa56a856485769d10f6aa581c5728653015d
I guess the change should have looked like this instead:
To Reproduce
Expected behavior
Test pods should not be created when tests are disabled.
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: