Splunk Operator: Allowing to set the security context for indexer pods

[ludo-zen]

Please select the type of request

Feature Request

Tell us more

Describe the request

• When an indexer is starting it mounts pvc volumes which have big size up to 64TB
  Sometimes when indexers restart they don't succeed to mount these pvc volumes
  We have this error below :

Unable to attach or mount volumes: unmounted volumes=[pvc-var], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

Expected behavior

• Indexers succeed to mount their pvc volumes quickly
  Like you already done for operator
  (

  splunk-operator/docs/ChangeLog.md

  Line 41 in 219d89c

  * CSPL_2532: Change fsGroupChangePolicy to `OnRootMismatch` for Splunk Enterprise and Splunk operator.

  )
  We would like to have the same for indexers

k8s by default forces persmissions. ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#configure-volume-permission-and-ownership-change-policy-for-pods

Define a security context for indexers,
crd has default value for fsGroupChangePolicy = "OnRootMismatch"

[ludo-zen]

• without that feature, in case the PVC is large (with lots of file), the PVC mounting process is very very slow
  So it will be very efficient and gain of time to have this feature up and running

[vivekr-splunk]

Hello lido-zen, we will look into the issue if it’s a bug we will fix this in 2.7.1 Thank you

…

On Fri, Dec 13, 2024 at 1:50 AM ludo-zen ***@***.***> wrote: - without that feature, in case the PVC is large (with lots of file), the PVC mounting process is very very slow So it will be very efficient and gain of time to have this feature up and running — Reply to this email directly, view it on GitHub <#1416 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWRQERYYFBBGPAK47LWL7ED2FKUVZAVCNFSM6AAAAABTRTDDG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRGAYTSNJXGE> . You are receiving this because you were assigned.Message ID: ***@***.***>