Content-Length: 236315 | pFad | http://github.com/splunk/splunk-operator/issues/1338

E1 Splunk Operator: Local Persistent Volume Provisioner · Issue #1338 · splunk/splunk-operator · GitHub
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Splunk Operator: Local Persistent Volume Provisioner #1338

Open
dnavaraWH opened this issue Jun 4, 2024 · 3 comments
Open

Splunk Operator: Local Persistent Volume Provisioner #1338

dnavaraWH opened this issue Jun 4, 2024 · 3 comments
Assignees
@vivekr-splunk
Labels
enhancement New feature or request

Comments

@dnavaraWH
Copy link

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

  • N/A

Reproduction/Testing steps

  • N/A

K8s environment

  • N/A
@dnavaraWH dnavaraWH changed the title Splunk Operator: Local Persistent Volume solution Splunk Operator: Local Persistent Volume Provisioner Jun 4, 2024
@vivekr-splunk vivekr-splunk added the enhancement New feature or request label Jun 4, 2024
@vivekr-splunk
Copy link
Collaborator

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

@yaroslav-nakonechnikov
Copy link

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
Copy link
Contributor

gjanders commented Jul 11, 2024 •
edited
Loading

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vivekr-splunk vivekr-splunk

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gjanders @jryb @vivekr-splunk @yaroslav-nakonechnikov @dnavaraWH








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/splunk/splunk-operator/issues/1338

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy