From 4aa2b6df61284f10fce9f9a4af99b3673e88e483 Mon Sep 17 00:00:00 2001
From: Sachin <57769917+slayer321@users.noreply.github.com>
Date: Sun, 25 Jul 2021 16:47:06 +0530
Subject: [PATCH] docs: mention container probes (#29085)

* mention container probe

* fix style errors

* fix errors
---
 content/en/docs/concepts/workloads/pods/_index.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/content/en/docs/concepts/workloads/pods/_index.md b/content/en/docs/concepts/workloads/pods/_index.md
index 5dd6bac9de..20dbdcb9e8 100644
--- a/content/en/docs/concepts/workloads/pods/_index.md
+++ b/content/en/docs/concepts/workloads/pods/_index.md
@@ -282,6 +282,17 @@ on the Kubernetes API server for each static Pod.
 This means that the Pods running on a node are visible on the API server,
 but cannot be controlled from there.
 
+## Container probes
+
+A _probe_ is a diagnostic performed periodically by the kubelet on a container. To perform a diagnostic, the kubelet can invoke different actions:
+
+- `ExecAction` (performed with the help of the container runtime)
+- `TCPSocketAction` (checked directly by the kubelet)
+- `HTTPGetAction` (checked directly by the kubelet)
+
+You can read more about [probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes) 
+in the Pod Lifecycle documentation.
+
 ## {{% heading "whatsnext" %}}
 
 * Learn about the [lifecycle of a Pod](/docs/concepts/workloads/pods/pod-lifecycle/).