Health Checks

All ESS services support and are configured with Kubernetes liveness, readiness and startup probes. These allow Kubernetes to check the health of each service, and automatically manage the lifecycle of ESS services, providing reliability and resiliency.

Startup probes

startupProbe:
  httpGet:
    path: /q/health/started
    port: 8443
    scheme: HTTPS
  failureThreshold: 120
  periodSeconds: 1

Startup probes allow Kubernetes to detect when a newly created container has completed starting up. Other probes will not be performed on it until it has finished starting up.

Readiness probes

livenessProbe:
  httpGet:
    path: /q/health/live
    port: 8443
    scheme: HTTPS
  timeoutSeconds: 1
  failureThreshold: 30
  periodSeconds: 10

Readiness probes indicate to Kubernetes that the service is ready and able to receive requests. A Pod with containers that are failing readiness probes will be removed from its associated Services, and thus will not receive requests until it returns to a ready state.

Liveness probes

readinessProbe:
  httpGet:
    path: /q/health/ready
    port: 8443
    scheme: HTTPS
  timeoutSeconds: 30
  periodSeconds: 10
  successThreshold: 1
  failureThreshold: 3

Liveness probes indicate to Kubernetes whether the container needs to be restarted.