Skip to content

Helm Chart affinity is not specific enough #17404

Open
@jirapong-opsta

Description

@jirapong-opsta

Describe the bug
The anti affinity on loki's ingester in the chart is not specific enough.

 ingester:
  affinity:
    podAntiAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        - labelSelector:
            matchLabels:
              app.kubernetes.io/component: ingester <- this label is not unique to Loki
          topologyKey: kubernetes.io/hostname

If mimir or tempo is installed alongside loki's ingester pods will be unable to be scheduled.

To Reproduce
Using helm:
Install mimir or tempo distributed first, then install Loki in distributed mode

Expected behavior
Loki ingester pods can be scheduled

Environment:

  • Infrastructure: K8s
  • Deployment tool: Helm

Metadata

Metadata

Assignees

No one assigned

    Labels

    LGTM stackIssues related to interoperability between Loki, Mimir, Tempoarea/helmtype/bugSomehing is not working as expected

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions