...
Liveness probes are used by the Kubernetes manager to monitor the real-time health of the containers in an ONAP deployment. If the liveness probe fails, Kubernetes will kill off the failed container and start a new container to replace it. The liveness probe have same parameters as the readiness probes described in the Deploy section. For example, to monitor the SDNC component has following liveness probe can be found in the SDNC DB deployment specification:livenessProbe: exec: command:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
livenessProbe: exec: command: ["mysqladmin", |
...
"ping"] |
...
initialDelaySeconds: |
...
30 periodSeconds: 10 timeoutSeconds: 5 |
Note that containers are inherently ephemeral so the healing action destroys failed containers and any state information within it. To avoid a loss of state, a persistent volume should be used to store all data that needs to be persisted over the re-creation of a container. Persistent volumes have been created for the database components of each of the projects and the same technique can be used for all persistent state information. 10 timeoutSeconds: 5