Ingest Role

[alwinmarkcf]

Hi,

I'm now wondering how the separation of roles is meant. So with the ES Operator, I can choose to spawn:

• client
• master
• data

where ES seems to have:

• node.master (default true)
• node.data (default true)
• node.ingest (default true)

As far as I could see with a first glance, that only the first two roles are handled.

What was the reason behind that? Wouldn't it make more sense to use the ES roles and spawn them dedicated, especially because of:

Ingest nodes are able to apply an ingest pipeline to a document in order to transform and enrich the document before indexing. With a heavy ingest load, it makes sense to use dedicated ingest nodes and to mark the master and data nodes as node.ingest: false.

https://www.elastic.co/guide/en/elasticsearch/reference/6.1/modules-node.html

It may also be this usecase is handled differently because the loadbalancer only talks to the client, but a clarification would be awesome

[stevesloka]

This this a new feature? I also don't see clients in that list on the docs page. Happy to add features as needed. =)

[karlskewes]

I think Elastic have just changed the naming scheme from client to ingest since the operator was created. They have done this from time to time. I use the current operator with custom 6.41 ES image and have an ingest/processor pipeline running on the client nodes.