You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tempo Helm chart with deploymentMode: Distributed and zoneAwareReplication enabled (default) generates Ingester StatefulSets with labels for rollout-operator. Ex here:
{{- if and .ctx.Values.ingester.zoneAwareReplication.enabled .rolloutZoneName }}
name: {{ printf "%s-%s" .component .rolloutZoneName }}
rollout-group: {{ .component }}
zone: {{ .rolloutZoneName }}
{{- end }}
This is identical to the issue filed against loki, here: grafana/loki#13168
Additionally, the anti-affinity rules for loki/tempo/mimir all incorporate the StatefulSet name. In all three cases it is explicitly set to the component name coupled with the target zone. When deploying multiple LTGM components to the same namespace this yields a first scheduled wins problem.
The text was updated successfully, but these errors were encountered:
Describe the bug
The
tempo
Helm chart withdeploymentMode: Distributed
andzoneAwareReplication
enabled (default) generates Ingester StatefulSets with labels for rollout-operator. Ex here:This is identical to the issue filed against loki, here: grafana/loki#13168
Additionally, the anti-affinity rules for loki/tempo/mimir all incorporate the StatefulSet name. In all three cases it is explicitly set to the
component
name coupled with the target zone. When deploying multiple LTGM components to the same namespace this yields a first scheduled wins problem.The text was updated successfully, but these errors were encountered: