Merge pull request #5228 from camilamacedo86/update-note-bootstrap-problem

📖 (doc): Update note about The Bootstrapping Problem

Author: k8s-ci-robot

docs/book/src/cronjob-tutorial/running-webhook.md

@@ -63,16 +63,17 @@ You can also try to create an invalid CronJob (e.g. use an ill-formatted
 schedule field). You should see a creation failure with a validation error.
 
 <aside class="warning">
-
 <h3>The Bootstrapping Problem</h3>
 
-If you are deploying a webhook for pods in the same cluster, be
-careful about the bootstrapping problem, since the creation request of the
-webhook pod would be sent to the webhook pod itself, which hasn't come up yet.
+When you deploy a webhook into the same cluster that it will validate, you can run into a *bootstrapping issue*:
+the webhook may try to validate the creation of its own Pod before it’s actually running.
+This can block the webhook from ever starting.
+
+To avoid this, make sure the webhook **ignores its own resources**.
+You can do this in one of two ways:
 
-To make it work, you can either use [namespaceSelector] if your kubernetes
-version is 1.9+ or use [objectSelector] if your kubernetes version is 1.15+ to
-skip itself.
+- **[namespaceSelector]** – label the namespace where the webhook runs and configure the webhook to skip it.
+- **[objectSelector]** – label the webhook’s own Pods or Deployments and exclude those objects directly.
 
 </aside>