How to resolve unsuccessful deployment to Liferay SaaS EXT environment due to liveness probe failure

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• While deploying a Client Extension to the Liferay SaaS EXT environment, the custom deployment keeps bootlooping with an error indicating Container <service-name> failed liveness probe, will be restarted

Environment

• Liferay SaaS EXT environment

Resolution

• In this particular case, the livenessProbe values in LCP.json might not be adequate for the Client Extension's deployment. The liveness probe is a feature in Liferay Cloud's self-healing functionality that ensures that a service is operation. However, in the case of custom deployments, it may be necessary to adjust the values and increase the livenessProbe value to ensure that it is not erroneously terminated and restarted.
• In certain cases, the readinessProbe values may need to be adjusted, to ensure that the service is responsive.

Additional Information

• How does the "environments" configuration on LCP.json work? (Liferay Learn documentation)
• Exceeded Quota Limit - Desired service spec cpu exceeded the max limit for provided plan on LXC EXT environment