Health check with Kubernetes probes

The Splunk Operator supports startup, liveness, and readiness probes with default values for Splunk Custom Resources.

Configurable probe parameters

You can modify the following probe configurations through Custom Resources:

  • initialDelaySeconds
  • timeoutSeconds
  • periodSeconds
  • failureThreshold

See the Kubernetes documentation for more information on startup, liveness, and readiness probes.

Default values

Probe Type initialDelaySeconds timeoutSeconds periodSeconds failureThreshold
Startup Probe 40 30 30 12
Readiness Probe 10 5 5 3
Liveness Probe 30 30 30 3

These defaults serve for most use cases. If you need to tune the values, the following example shows how to modify the defaults.

Example probe configuration

CODE 
apiVersion: enterprise.splunk.com/v4
kind:  Standalone
metadata:
  name: example
  finalizers:
  - enterprise.splunk.com/delete-pvc
spec:
  replicas: 1
  startupProbe:
    initialDelaySeconds: 40
    timeoutSeconds: 30
    periodSeconds: 30
    failureThreshold: 12
  livenessProbe:
    initialDelaySeconds: 30
    timeoutSeconds: 30
    periodSeconds: 30
    failureThreshold: 3
  readinessProbe:
    initialDelaySeconds: 10
    timeoutSeconds: 5
    periodSeconds: 5
    failureThreshold: 3