From eec25be11ae9fe3db18fed2b5dce953f039fe47b Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Sun, 22 Aug 2021 19:35:58 -0700 Subject: [PATCH] Change heading level --- .../en/monitoring-alerting/how-monitoring-works/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.5/en/monitoring-alerting/how-monitoring-works/_index.md b/content/rancher/v2.5/en/monitoring-alerting/how-monitoring-works/_index.md index a9c205ba2c6..79738b202b0 100644 --- a/content/rancher/v2.5/en/monitoring-alerting/how-monitoring-works/_index.md +++ b/content/rancher/v2.5/en/monitoring-alerting/how-monitoring-works/_index.md @@ -142,7 +142,7 @@ For more information on `node-exporter`, refer to the [upstream documentation.]( [kube-state-metrics](https://github.com/kubernetes/kube-state-metrics) is also useful because it exports metrics for Kubernetes components. -# 4.4. Components Exposed in the Rancher UI +### 4.4. Components Exposed in the Rancher UI When the monitoring application is installed, you will be able to edit the following components in the Rancher UI: @@ -248,4 +248,4 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **kubelet:** The internal Kubernetes component that watches the API server for pods on a node and makes sure they are running. - **ingress-nginx:** An Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer. - **coreDns/kubeDns:** The internal Kubernetes component responsible for DNS. -- **kube-api-server:** The main internal Kubernetes component that is responsible for exposing APIs for the other master components. \ No newline at end of file +- **kube-api-server:** The main internal Kubernetes component that is responsible for exposing APIs for the other master components.