helm -n <namespace> install <your-clusterName> -f values.yaml splunk-otel-collector-chart/splunk-otel-collector
kubectl -n <namespace> get pods
NAME READY STATUS RESTARTS AGE otel-splunk-otel-collector-agent-cdtp6 0/1 CrashLoopBackOff 21 (71s ago) 86m
kubectl -n <namespace> logs -f <collector-agent-pod>If you see an error similar to below in the agent pod logs it indicates the agent pod security context is not allowing the pod to write to hostPath:
2023-12-18T07:07:11.388Z info service@v0.88.0/service.go:192 Shutdown complete. Error: cannot start pipelines: storage client: open /var/addon/splunk/otel_pos/receiver_filelog_: permission denied 2023/12/18 07:07:11 main.go:94: application run finished with error: cannot start pipelines: storage client: open /var/addon/splunk/otel_pos/receiver_filelog_: permission denied
################################################################################ # Kubernetes distribution being run. Leave empty for other. # - "aks" (Azure Kubernetes Service) # - "eks" (Amazon Elastic Kubernetes Service) # - "eks/fargate" (Amazon Elastic Kubernetes Service with Fargate profiles ) # - "gke" (Google Kubernetes Engine / Standard mode) # - "gke/autopilot" (Google Kubernetes Engine / Autopilot mode) # - "openshift" (RedHat OpenShift) ################################################################################distribution: ""Default securityContext.runAsUser configuration snippet:
securityContext: {}
# runAsUser: 20000
# runAsGroup: 20000
The pods can fail to install due to the permissions not being correctly set. The Openshift Security Context Constraints (SCC) are created automatically when the distribution: is correctly configured to openshift in the values.yaml file, by default this value is empty. To set the distribution to OpenShift configure the distribution line as follows:
distribution: "openshift"
The default values for the Security Context Constraints are found in the securityContextConstraints.yaml
If the securityContext.runAsUser has been changed please note that running the collector agent for log collection in non-root mode is not currently supported in OpenShift environments and will result in the pod failing to install or start. This is noted in the advanced-configuraiton.md
Ensure the securityContext.runAsUser is configured in the values.yaml file as per the default below:
securityContext: {}
# runAsUser: 20000
# runAsGroup: 20000
There is currently an Ideas page for support for non-root mode for Openshift. If you are interested in support for non-root mode for Openshift to be implemented, please click the vote button that can be found at the ideas page link: Splunk Ideas Page (SFXIMMID-I-470) - Run Otel agent as non-root user
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |