It's hard to tell because it looks like the formatting was lost in the copy and paste (you can use code blocks with three `s btw), but I think multiple concepts might be conflated. The actual beta operator stateful set does not need persistent storage. The volume claim templates inside of the Elasticsearch resource (separate from the operator statefulset) can be configured like so: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-volume-claim-templates.html
When I am trying to start the Elasticsearch master and date cluster I get the unbound persistentvolumeclaims error. How do i get pvc in the same pods as elasticsearch eck k8s. He functional in hospath normally when i create nfs he give me unbound persistentvolumeclaims error. Is it possible to have us claimName on the same pod?
Unless you have a good reason to do so (like no volume provisioner), you should probably not define PersistentVolumeClaims and mount them in the spec yourself. Instead, you can just declare the claim template. ECK and the StatefulSet controller will take care of creating the PersistentVolumeClaim based on that template automatically. See this doc.
You don't have to set discovery.zen.ping.unicast.hosts, discovery.zen.minimum_master_nodes and node.name. ECK is already doing that for you.
ECK is compatible with any PersistentVolume provider implementation.
If you don't have a dynamic provisioner for NFS volumes, you should be able to manually create your own PersistentVolumes with an NFS spec. This video gives an example.
However, we strongly recommend you not to use NFS with Elasticsearch. It usually leads to bad performance.