Update docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc

eedugon · gizas · web-flow · commit 99ff11f07ba7 · 2024-11-04T09:50:50.000+01:00
Co-authored-by: Andrew Gizas &lt;andreas.gkizas@elastic.co&gt;
diff --git a/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc b/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc
@@ -919,7 +919,7 @@ In an already installed system, the API Key is stored in a `Secret` named `elast
 +
 These metrics (`state_*`) are retrieved by one of the Pods acting as `leader` (as described in <<running-on-kubernetes-standalone>>), so in order to troubleshoot that situation:
 +
-. Determine which Pod owns the leadership `lease` in the cluster, with:
+. Determine which Pod owns the [leadership](https://www.elastic.co/guide/en/fleet/current/kubernetes_leaderelection-provider.html#:~:text=Provides%20the%20option%20to%20enable,Elastic%20Agent%20holds%20the%20leadership.) `lease` in the cluster, with:
 +
 [source,sh]
 ----

Original file line number	Diff line number	Diff line change
@@ -919,7 +919,7 @@ In an already installed system, the API Key is stored in a `Secret` named `elast
`919`	`919`	`+`
`920`	`920`	These metrics (`state_*`) are retrieved by one of the Pods acting as `leader` (as described in <<running-on-kubernetes-standalone>>), so in order to troubleshoot that situation:
`921`	`921`	`+`
`922`		-. Determine which Pod owns the leadership `lease` in the cluster, with:
	`922`	+. Determine which Pod owns the [leadership](https://www.elastic.co/guide/en/fleet/current/kubernetes_leaderelection-provider.html#:~:text=Provides%20the%20option%20to%20enable,Elastic%20Agent%20holds%20the%20leadership.) `lease` in the cluster, with:
`923`	`923`	`+`
`924`	`924`	`[source,sh]`
`925`	`925`	`----`