search

splunk / splunk-operator

Splunk Operator for Kubernetes
Other
206 stars 114 forks source link

Splunk Operator: Local Persistent Volume Provisioner #1338

Open dnavaraWH opened 4 months ago

dnavaraWH commented 4 months ago

Please select the type of request

Feature Request

Tell us more

Describe the request I would like for the Splunk-operator team to create their own local provisioner or actively contribute to one of the local provisioners such as https://github.com/topolvm/topolvm or https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner

Splunk requires ( suggests ) that local persistent volume is used for Indexer hot cache, however Splunk doesn't provide a provisioner. Issue with the above mentioned provisioners is their speed of delivery and updates.

Expected behavior I want a local provisioner that is actively developed/maintained by Splunk team to ensure best practices and latest Kubernetes compatibility.

Splunk setup on K8S

Reproduction/Testing steps

K8s environment

vivekr-splunk commented 4 months ago

@dnavaraWH this is really needed request. we will investigate and get back to you on this. thank you for raising this request

yaroslav-nakonechnikov commented 4 months ago

with local storage we played a lot, and we utilized instances with ephemeral storage. also, as i understand, you can define custom storageclass with your needs, which then will be used by splunk-operator.

but i strongly agree, that there are very few ways to configure storage as you want to.

gjanders commented 2 months ago

I recently did a writeup on the storage we intend to move the cluster managers to in the near future https://medium.com/@gjanders03/kubernetes-storage-performance-comparison-rook-ceph-and-piraeus-datastore-linstor-e9bc2859a8f0 Along with standalone search heads and pull-based heavy forwarders

I'm using the sig-storage-local-static-provisioner for indexers and all instances currently which does appear to have a recent update which is great