Open lindeskar opened 4 months ago
My suggested fix; use loki.ingesterFullname
in the rollout-group label: https://github.com/grafana/loki/pull/13170
I'm having the same issue, would it be possible for a maintainer to review the PR @lindeskar opened?
I am also facing this issue. I don't see a workaround since ingester anti-affinity rules are ignored with zoneAwareReplication enabled. Disabling rollout_operator also does not remove the rollout-group: ingester labels from Loki ingester pods.
Edit: Workaround was to use kustomize and change the rollout-group label to loki-ingester
for all relevant loki resources.
Describe the bug The
loki
Helm chart withdeploymentMode: Distributed
andzoneAwareReplication
enabled (default) generates Ingester StatefulSets with labels for rollout-operator. Ex.:https://github.com/grafana/loki/blob/9c96d26895cbb56ed31cafb247c28404ac1caaef/production/helm/loki/templates/ingester/statefulset-ingester-zone-a.yaml#L61-L62
The mimir-distributed Helm chart generates StatefulSets with the same label values. Ex. mimir-ingester-zone-a-0:
Deploying the two charts to the same Namespace means rollout-operator will select both Mimir and Loki StatefulSets and get confused about the rollout status. For me one of the Mimir Ingester Pods is constantly being recreated.
To Reproduce Steps to reproduce the behavior:
mimir-distributed
chart with default valuesloki
chart with distributed-values.yamlExpected behavior rollout-operator handles Mimir and Loki Ingesters as separate rollout-groups.
Environment:
Screenshots, Promtail config, or terminal output From
rollout-operator
Pod: