Add warning that liveness probe must be configured carefully (#39930)

* a warning on liveness probes about cascading failures, added

* A warning that liveness probe must be configured carefully.

* better words are added

* wrapping of the log lines

* warning is modified that liveness probe must be configured carefully

Author: KanishkaVerma054

content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

@@ -14,6 +14,10 @@ where an application is running, but unable to make progress. Restarting a
 container in such a state can help to make the application more available
 despite bugs.
 
+A common pattern for liveness probes is to use the same low-cost HTTP endpoint
+as for readiness probes, but with a higher failureThreshold. This ensures that the pod
+is observed as not-ready for some period of time before it is hard killed.
+
 The kubelet uses readiness probes to know when a container is ready to start
 accepting traffic. A Pod is considered ready when all of its containers are ready.
 One use of this signal is to control which Pods are used as backends for Services.
@@ -25,7 +29,18 @@ it succeeds, making sure those probes don't interfere with the application start
 This can be used to adopt liveness checks on slow starting containers, avoiding them
 getting killed by the kubelet before they are up and running.
 
+{{< caution >}}
+Liveness probes can be a powerful way to recover from application failures, but
+they should be used with caution. Liveness probes must be configured carefully
+to ensure that they truly indicate unrecoverable application failure, for example a deadlock.
+{{< /caution >}}
 
+{{< note >}}
+Incorrect implementation of liveness probes can lead to cascading failures. This results in
+restarting of container under high load; failed client requests as your application became less
+scalable; and increased workload on remaining pods due to some failed pods.
+Understand the difference between readiness and liveness probes and when to apply them for your app.
+{{< /note >}}
 
 ## {{% heading "prerequisites" %}}