# Configure Container Probes

These instructions demonstrate how to configure liveness, readiness and startup probes for containers.

The time-related parameters of the Liveness, Readiness, and Startup probes can be configured through `aggregatorSpec.readinessProbeSpec/livenessProbeSpec/startupProbeSpec` and `leafSpec.readinessProbeSpec/livenessProbeSpec/startupProbeSpec`.

**Note**: Liveness probes are disabled by default as of [Operator 3.0.96](https://docs.singlestore.com/db/v9.1/release-notes/singlestore-kubernetes-operator-release-notes.md) and later. You can enable them if needed using the following configuration.

```yaml
aggregatorSpec:
  readinessProbeSpec:
    initialDelaySeconds: 10
    timeoutSeconds: 1
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 3
  livenessProbeSpec:
    initialDelaySeconds: 10
    timeoutSeconds: 1
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 3
  startupProbeSpec:    
    initialDelaySeconds: 10
    timeoutSeconds: 1      
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 30
leafSpec:
  readinessProbeSpec:
    initialDelaySeconds: 10
    timeoutSeconds: 1
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 3
  livenessProbeSpec:
    initialDelaySeconds: 10
    timeoutSeconds: 1
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 3
  startupProbeSpec:
    initialDelaySeconds: 10
    timeoutSeconds: 1
    periodSeconds: 10
    successThreshold: 1
    failureThreshold: 30

```

Refer to the [Kubernetes documentation](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/) for more information about these attributes.

## Configure Liveness Probe

The Operator can be configured to create liveness probes on the pods in the cluster. This feature attempts to restart a container if it fails a probe. This feature is off by default as thread, CPU, or PID exhaustion from database workloads can lead to restarts.

```yaml
spec:
  enableLivenessProbeOnNodes: true

```

## When to Override Startup Probe Defaults

Startup probes are particularly useful in the following scenarios:

* SingleStore nodes require long initialization times (for example, large caches or recovery operations)
* You want to prevent premature restarts during cluster startup or recovery
* Child aggregators require additional time to become ready before receiving traffic

***

Modified at: April 17, 2026

Source: [/db/v9.1/reference/singlestore-operator-reference/configure-container-probes/](https://docs.singlestore.com/db/v9.1/reference/singlestore-operator-reference/configure-container-probes/)

(An index of the documentation is available at /llms.txt)