public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix broken links - Part 7 (#646)

Browse Source 
* Fix links

* Apply suggestions from code review

Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>

---------

Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
This commit is contained in:
Billy Tat
2023-06-01 18:02:46 -04:00
committed by GitHub
co-authored by Marty Hernandez Avedon
parent 7be7b1c337
commit 2352ff4b4f
31 changed files with 61 additions and 68 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/reference-guides/cluster-configuration/rancher-server-configuration/use-existing-nodes/rancher-agent-options.md
+1 -1
View File
@@ -4,7 +4,7 @@ title: Rancher Agent Options
Rancher deploys an agent on each node to communicate with the node. This pages describes the options that can be passed to the agent. To use these options, you will need to [create a cluster with custom nodes](../../../../pages-for-subheaders/use-existing-nodes.md) and add the options to the generated `docker run` command when adding a node.
For an overview of how Rancher communicates with downstream clusters using node agents, refer to the [architecture section.](../../../../pages-for-subheaders/rancher-manager-architecture.md#3-node-agents)
For an overview of how Rancher communicates with downstream clusters using node agents, refer to the [architecture section.](../../../rancher-manager-architecture/communicating-with-downstream-user-clusters.md#3-node-agents)
## General options
versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/examples.md
+1 -1
View File
@@ -20,4 +20,4 @@ An example PrometheusRule is on [this page.](https://github.com/prometheus-opera
### Alertmanager Config
For an example configuration, refer to [this section.](../../how-to-guides/advanced-user-guides/monitoring-v2-configuration-guides/advanced-configuration/alertmanager.md#example-alertmanager-config)
For an example configuration, refer to [this section](./receivers.md#example-alertmanager-configs).
versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/receivers.md
+1 -1
View File
@@ -364,7 +364,7 @@ spec:
# key: string
```
For more information on enabling alerting for `rancher-cis-benchmark`, see [this section.](../../pages-for-subheaders/cis-scan-guides.md#enabling-alerting-for-rancher-cis-benchmark)
For more information on enabling alerting for `rancher-cis-benchmark`, see [this section.](../../how-to-guides/advanced-user-guides/cis-scan-guides/enable-alerting-for-rancher-cis-benchmark.md)
## Trusted CA for Notifiers
versioned_docs/version-2.5/reference-guides/monitoring-v2-configuration/routes.md
+1 -1
View File
@@ -34,7 +34,7 @@ Annotations should be used for information that does not affect who receives the
<TabItem value="Rancher v2.5.4+">
### Receiver
The route needs to refer to a [receiver](#receiver-configuration) that has already been configured.
The route needs to refer to a [receiver](./receivers.md) that has already been configured.
### Grouping