Skip to content

Conversation

grenzr
Copy link

@grenzr grenzr commented Jul 30, 2019

If you're running a mixed linux/windows cluster and using the Elasticsearch-operator or elasticsearch helm charts, you're going to need to peg es-operator itself to a linux node as the image for it is Linux only.

This PR also 👍

  • fixes nodeSelector to Linux OS for Kibana/Cerebro deployments, and adds nodeSelector configuration to the elastic search chart (already plumbed into ElasticsearchCluster CRD, but config was missing in the chart to use it).
  • adds missing master-volume-size config properly to the elasticsearch helm chart

I'm making use of another useful PR added by @komljen so that I can leverage nodeSelector to bring up ES nodes on Linux machines too.
His PR has yet to be merged here #312 - I'll fix this branch if that gets merged first, but I need it right now so I'm leaving it here for now until a maintainer responds on this PR).

grenzr and others added 7 commits July 30, 2019 15:11
This is needed to stop it trying to spin up on windows nodes in mixed
cluster scenarios.
Includes nodeSelector support
This is so that deployments on mixed Kubernetes clusters will bring up
these services on Linux only.
Impossible to use the feature in the CRD without this
@grenzr grenzr changed the title es-operator itself needs nodeSelector for k8s mixed clusters es-operator + elasticsearch helm charts nodeSelector for k8s mixed clusters Aug 7, 2019
grenzr added 2 commits August 9, 2019 11:46
Missing property which is used in es-operator to define master volume
sizes in the pvc.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants