From 0b1a9b0d3545c0cad2371bdf1e77d6b62b9fda35 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Wed, 20 Nov 2024 13:41:56 -0800 Subject: [PATCH 1/2] Remove duplicate image caption --- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- .../kubernetes-cluster-setup/high-availability-installs.md | 2 -- 14 files changed, 28 deletions(-) diff --git a/archived_docs/en/version-2.0-2.4/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/archived_docs/en/version-2.0-2.4/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/archived_docs/en/version-2.0-2.4/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/archived_docs/en/version-2.0-2.4/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/docs/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/docs/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 52841cefbcf6..c53bf4de7317 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 52841cefbcf6..c53bf4de7317 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 2f28274e31b8..174b30daa339 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 2f28274e31b8..174b30daa339 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 52841cefbcf6..c53bf4de7317 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index 2f28274e31b8..174b30daa339 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个 - Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。 - Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。 -
使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：
- ![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg) 使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止 diff --git a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.10/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.5/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.5/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.5/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.5/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.6/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.8/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers diff --git a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md index a287c374fe34..7c17df3ed144 100644 --- a/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md +++ b/versioned_docs/version-2.9/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md @@ -23,7 +23,5 @@ For information on how Rancher works, regardless of the installation method, ref - The Ingress controller will redirect HTTP to HTTPS and terminate SSL/TLS on port TCP/443. - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment. -
Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers
- ![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg) Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers From 8bf8fef3ba6abc104a12f150b1b762edb49f1cb7 Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Fri, 22 Nov 2024 10:58:26 -0800 Subject: [PATCH 2/2] Remove figcaption that has no associated image --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- .../monitoring-and-alerting/how-monitoring-works.md | 3 --- 13 files changed, 39 deletions(-) diff --git a/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 3a2ec873a292..8e860dcd9326 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的 - 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。 -
数据如何流经 Monitoring 应用程序
- - ## 2. Prometheus 的工作原理 ### 存储时间序列数据 diff --git a/versioned_docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/versioned_docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/versioned_docs/version-2.5/explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.5/explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 152275652aca..a2a495f00d8c 100644 --- a/versioned_docs/version-2.5/explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.5/explanations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/versioned_docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/versioned_docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data diff --git a/versioned_docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 8f14e7faa069..f98ef8a8762b 100644 --- a/versioned_docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -61,9 +61,6 @@ Once Prometheus determines that an alert needs to be fired, alerts are forwarded - Routes and receivers are also stored in the Kubernetes API via the Alertmanager Secret. When the Secret is updated, Alertmanager is also updated automatically. Note that routing occurs via labels only (not via annotations, etc.). -
How data flows through the monitoring application:
- - ## 2. How Prometheus Works ### Storing Time Series Data