Skip to content
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] tempo Ingester rollout-group collides with other LTGM component ingesters #3442

Open
boldfield opened this issue Nov 21, 2024 · 0 comments · May be fixed by #3443
Open

[Helm] tempo Ingester rollout-group collides with other LTGM component ingesters #3442

boldfield opened this issue Nov 21, 2024 · 0 comments · May be fixed by #3443

Comments

@boldfield
Copy link

Describe the bug

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant