# External provisioner is not creating volume

**URL:** <https://discuss.elastic.co/t/external-provisioner-is-not-creating-volume/285762>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [October 3, 2021, 8:48am UTC](https://discuss.elastic.co/t/external-provisioner-is-not-creating-volume/285762 "2021-10-03T08:48:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [October 4, 2021, 8:50am UTC](https://discuss.elastic.co/t/external-provisioner-is-not-creating-volume/285762/3 "2021-10-04T08:50:14Z")

</div>

I can't really help with the NFS storage provisioner and it would probably be good to engage with NFS provisioner project. I noticed however that the nfs-client-provisioner project is deprecated.

There is another more fundamental issue here and that is that it is not recommended to use NFS volumes for the Elasticsearch data volume to begin with. This [discussion thread](https://discuss.elastic.co/t/why-nfs-is-to-be-avoided-for-data-directories/215240/3) offers a bit more context as to why that is the case and it is also mentioned in the [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/tune-for-indexing-speed.html),

---

_[View the full topic](https://discuss.elastic.co/t/external-provisioner-is-not-creating-volume/285762)._