docs: update mutual TLS reference in high availability documentation

[TheMeier]

Fixes: #5109

Pull Request Checklist

Please check all the applicable boxes.

• Please list all open issue(s) discussed with maintainers related to this change
  • Fixes broken links to "secure cluster traffic" #5109
• I have added/updated the required documentation
• I have signed-off my commits
• I will follow best practices for contributing to this project

Which user-facing changes does this PR introduce?

NONE

Summary by CodeRabbit

• Documentation
  • Updated the mutual TLS reference in the high-availability guide to point to the external Prometheus “Gossip Traffic” documentation.
  • Updated the “Further Reading” entry to link to the GitHub-hosted Secure Cluster Traffic design document for additional details.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 382d70ed-ff65-4899-823f-30ff70732ae8

📥 Commits

Reviewing files that changed from the base of the PR and between 4fc00c0 and d436e31.

📒 Files selected for processing (1)

• docs/high_availability.md

✅ Files skipped from review due to trivial changes (1)

• docs/high_availability.md

---

📝 Walkthrough

Walkthrough

A broken documentation link in the high availability guide was corrected. The internal reference to a non-existent secure cluster traffic design document was replaced with an external Prometheus documentation link pointing to the Gossip Traffic section for mutual TLS configuration.

Changes

Cohort / File(s)	Summary
Documentation Link Fix docs/high_availability.md	Replaced internal broken link (../doc/design/secure-cluster-traffic.md) with external Prometheus "Gossip Traffic" URL for mutual TLS in the "Security" section; updated "Further Reading" entry to the GitHub-hosted secure-cluster-traffic.md URL.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hopped through docs with careful ears,

Found a path that led to tears.
Swapped the broken for the true,
Now the cluster hops anew. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating mutual TLS references in high availability documentation.
Description check	✅ Passed	The description includes the linked issue (#5109), completes relevant checklist items, and indicates no user-facing changes.
Linked Issues check	✅ Passed	The PR updates broken links in docs/high_availability.md to point to correct documentation, directly addressing issue #5109's requirement to fix 404 errors.
Out of Scope Changes check	✅ Passed	All changes are focused on fixing broken documentation links in high_availability.md, with no unrelated modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docs/high_availability.md (1)

482-484: ⚠️ Potential issue | 🟠 Major

Another broken secure-cluster-traffic reference remains in “Further Reading.”

Line 483 still points to ../doc/design/secure-cluster-traffic.md, which resolves to a 404. This leaves the linked issue only partially fixed in this file.

Suggested doc fix

-- [Secure Cluster Traffic Design](../doc/design/secure-cluster-traffic.md)
+- [Gossip Traffic (mutual TLS)](https://prometheus.io/docs/alerting/latest/https/#gossip-traffic)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/high_availability.md` around lines 482 - 484, Update the broken link
"../doc/design/secure-cluster-traffic.md" in the "Further Reading" list so it
points to the correct relative location of the secure-cluster-traffic doc
(replace the broken target string "../doc/design/secure-cluster-traffic.md" with
the correct path, e.g., "design/secure-cluster-traffic.md" or
"./design/secure-cluster-traffic.md") in docs/high_availability.md where the
list item currently appears.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/high_availability.md`:
- Line 364: The sentence "See [Gossip
Traffic](https://prometheus.io/docs/alerting/latest/https/#gossip-traffic)
section for configuration mutual TLS." is awkward; change it to a clearer
phrasing such as "See the Gossip Traffic section for configuring mutual TLS" or
"See the Gossip Traffic section for mutual TLS configuration" to improve
readability and grammar.

---

Outside diff comments:
In `@docs/high_availability.md`:
- Around line 482-484: Update the broken link
"../doc/design/secure-cluster-traffic.md" in the "Further Reading" list so it
points to the correct relative location of the secure-cluster-traffic doc
(replace the broken target string "../doc/design/secure-cluster-traffic.md" with
the correct path, e.g., "design/secure-cluster-traffic.md" or
"./design/secure-cluster-traffic.md") in docs/high_availability.md where the
list item currently appears.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 8cd687b1-a189-4f24-a484-bcb6718892ef

📥 Commits

Reviewing files that changed from the base of the PR and between 4189528 and 4fc00c0.

📒 Files selected for processing (1)

• docs/high_availability.md