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 }}
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.
Describe the bug
The
tempoHelm chart withdeploymentMode: DistributedandzoneAwareReplicationenabled (default) generates Ingester StatefulSets with labels for rollout-operator. Ex here:This is identical to the issue filed against loki, here: https://github.com/grafana/loki/issues/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
componentname coupled with the target zone. When deploying multiple LTGM components to the same namespace this yields a first scheduled wins problem.