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] when deployed with multiple LGTM components in one namespace Ingester naming causes conflicts #15062

Open
boldfield opened this issue Nov 22, 2024 · 0 comments · May be fixed by #15063
Open
Labels
area/helm type/bug Somehing is not working as expected

Comments

@boldfield
Copy link

Describe the bug
When deploying multiple distributed LTGM stack components to a single namespace the anti-affinity rules of each component's conflict with each other. E.g. here:

        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: rollout-group
                    operator: In
                    values:
                      - ingester
                  - key: name
                    operator: NotIn
                    values:
                      - ingester-zone-a

To Reproduce
Steps to reproduce the behavior:

  1. Deploy distributed Loki, Tempo, and Mimir to a single Kubernetes namespace
  2. watch scheduling failures due to podAntiAffinity rule conflicts

Expected behavior
All ingester components schedule successfully schedule and deploy

Environment:

  • Infrastructure: Kubernetes
  • Deployment tool: helm

Screenshots, Promtail config, or terminal output
N/A

@JStickler JStickler added area/helm type/bug Somehing is not working as expected labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm type/bug Somehing is not working as expected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants