Closed rocketraman closed 6 years ago
Specs, especially master and data deployments and stateful sets, should probably include a pod anti-affinity configuration, to avoid scheduling multiple pods onto the same nodes. For example:
affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchExpressions: - key: "component" operator: In values: - "elasticsearch" - key: "role" operator: In values: - "data" topologyKey: "kubernetes.io/hostname"
As documented in https://github.com/pires/kubernetes-elasticsearch-cluster#pod-anti-affinity?
You do have a point in adding key component. Please, do open a PR. Happy to review :)
component
Specs, especially master and data deployments and stateful sets, should probably include a pod anti-affinity configuration, to avoid scheduling multiple pods onto the same nodes. For example: