Skip to content

Commit ca1e7e5

Browse files
committed
Fix links
1 parent ff1369e commit ca1e7e5

File tree

2 files changed

+3
-1
lines changed
  • content/rancher/v2.5/en
    • best-practices/rancher-managed/monitoring
    • installation/resources/tls-secrets

2 files changed

+3
-1
lines changed

content/rancher/v2.5/en/best-practices/rancher-managed/monitoring/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ aliases:
77

88
Configuring sensible monitoring and alerting rules is vital for running any production workloads securely and reliably. This is not different when using Kubernetes and Rancher. Fortunately the integrated monitoring and alerting functionality makes this whole process a lot easier.
99

10-
The [Rancher Documentation]({{<baseurl>}}/rancher/v2.5/en/monitoring-alerting/v2.5/) describes in detail, how you can set up a complete Prometheus and Grafana stack. Out of the box this will scrape monitoring data from all system and Kubernetes components in your cluster and provide sensible dashboards and alerts for them to get started. But for a reliable setup, you also need to monitor your own workloads and adapt Prometheus and Grafana to your own specific use cases and cluster sizes. This document aims to give you best practices for this.
10+
The [Rancher monitoring documentation]({{<baseurl>}}/rancher/v2.5/en/monitoring-alerting/) describes how you can set up a complete Prometheus and Grafana stack. Out of the box this will scrape monitoring data from all system and Kubernetes components in your cluster and provide sensible dashboards and alerts for them to get started. But for a reliable setup, you also need to monitor your own workloads and adapt Prometheus and Grafana to your own specific use cases and cluster sizes. This document aims to give you best practices for this.
1111

1212
- [What to Monitor](#what-to-monitor)
1313
- [Configuring Prometheus Resource Usage](#configuring-prometheus-resource-usage)

content/rancher/v2.5/en/installation/resources/tls-secrets/_index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
title: Adding TLS Secrets
33
weight: 2
4+
aliases:
5+
- /rancher/v2.5/en/installation/resources/encryption/tls-secrets/
46
---
57

68
Kubernetes will create all the objects and services for Rancher, but it will not become available until we populate the `tls-rancher-ingress` secret in the `cattle-system` namespace with the certificate and key.

0 commit comments

Comments
 (0)