Configuring Probes in Kubernetes

To perform health checks in Kubernetes, configure the following probes:

  • Liveness probe: This indicates when a container restarts.

  • Readiness probe: This indicates when a container is ready to start accepting traffic.

  • Startup probe: It checks if the application in a container is started.

The HTTP endpoint in the TIBCO BusinessWorks Container Edition application is used to configure readiness probes in Kubernetes. The endpoint must be accessed only after the application is started.

 

Setting Up Liveness Probe

To view the liveness of an application, you need to add the liveness probe in the manifest.yml file.

livenessProbe:
 httpGet:
   path: /health/liveness
   port: 8090

For more information, see the "Configure Liveness, Readiness, and Startup Probes" topic in the Kubernetes documentation.

Note: The liveness probe fails only if the container is unhealthy or non-responsive.

Setting Up Readiness Probe

To view the readiness of an application, you must add the readiness probe in the manifest.yml file.

readinessProbe:
 # an http probe
 httpGet:
   path: /health/readiness
   port: 8090

For more information, see the "Configure Liveness, Readiness, and Startup Probes" topic in the Kubernetes documentation.

Setting Up Startup Probe

To view the startup of an application, you need to add the startup probe in the manifest.yml file.

startupProbe:
 # an http probe
 httpGet:
   path: /health/startup
   port: 8090

For more information, see the "Configure Liveness, Readiness, and Startup Probes" topic in the Kubernetes documentation.