How can we mount NFS mount on elastic operator based pods (Elasticsearch on Kubernetes)

[pebrc (Peter Brachwitz)]

I am not sure I fully understand your question. What do you mean by

@nethisandeep

it's only possible to attach storage volume and cloud plugins for backup storage.

There is no such restriction. You can mount anything to the pods as you have full access to the podTemplate.

But we don't recommend using NFS for the Elasticsearch data directory for performance reasons. Now you mention "backup" and I am not sure how to understand that. Two thoughts on that though:

1. Elasticsearch has built-in redundancy if you configure your indices to have replicas that provide some form of "backup" in case a node fails.
2. Elasticsearch comes with a snapshot mechanism that allows you together with Snapshot Lifecycle Management to create backups of your data in regular intervals. You can choose from a variety of storage solutions for the snapshot repository (AWS S3, Azure, Google Storage, HDFS, Openstack Swift)

Please also have a look this related answer from @sebgl that gives a good overview of possible approaches to storage on ECK:

Best option for persistent volume of an on-premise ECK

Hi @Ali_Reza_Haghighat, You're right: we do not recommend NFS, which generally offers poor performance for Elasticsearch. We also have problems using Local volume (Pod crashes after a few document insertion) This seems a bit strange. How are you handling the local volumes? A few options you may want to look at: If you have any network-attached PersistentVolume provider available, that's by far the easiest option. GCP persistent disks and AWS ELBs now offer pretty good performance, depend…