CHAPTER 6. MONITORING APPLICATION HEALTH BY USING HEALTH CHECKS 2 The liveness probe. 1 The readiness probe. To configure readiness, liveness, and startup probes, add one or more probes to the specification for the pod that contains the container which you want to perform the health checks If you want to add or edit health checks in an existing pod, you must edit the pod  DeploymentConfig  object or use the  Developer  perspective in the web console. You cannot use the CLI to add or edit health checks for an existing pod. To add probes for a container: NOTE Procedure 6.2. CONFIGURING HEALTH CHECKS USING THE CLI 1. Create a  Pod  object to add one or more probes: 99 kind: Deployment apiVersion: apps/v1 ... spec: ... template: spec: containers: - resources: {} readinessProbe:  1 tcpSocket: port:  8080 timeoutSeconds:  1 periodSeconds:  10 successThreshold:  1 failureThreshold:  3 terminationMessagePath: /dev/termination-log name: ruby-ex livenessProbe:  2 tcpSocket: port:  8080 initialDelaySeconds:  15 timeoutSeconds:  1 periodSeconds:  10 successThreshold:  1 failureThreshold:  3 ... apiVersion: v1 kind: Pod metadata: labels: