Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Kibana chart setting "podAntiAffinity" is useless. #318

Closed
nerddelphi opened this issue Oct 10, 2019 · 1 comment · Fixed by #326
Closed

Kibana chart setting "podAntiAffinity" is useless. #318

nerddelphi opened this issue Oct 10, 2019 · 1 comment · Fixed by #326
Assignees
Labels
enhancement New feature or request

Comments

@nerddelphi
Copy link

nerddelphi commented Oct 10, 2019

That line is useless, once deployment template doesn't read that config, causing pods be scheduled in the same nodes:

antiAffinityTopologyKey: "kubernetes.io/hostname"

That setting could be copied from elasticsearch chart:

{{- if eq .Values.antiAffinity "hard" }}

@jmlrt jmlrt self-assigned this Oct 14, 2019
@jmlrt jmlrt added the enhancement New feature or request label Oct 14, 2019
@jmlrt
Copy link
Member

jmlrt commented Oct 14, 2019

Hi @nerddelphi, thank you for reporting this issue.

antiAffinity and antiAffinityTopologyKey are a heritage from Elasticsearch chart but aren't used for Kibana chart as Kibana clustering is currently not supported.

I created #326 to remove these keys.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants