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 1a34415ea58..99c7c066cfd 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 @@ -210,13 +210,13 @@ Certain internal Kubernetes components are scraped via a proxy deployed as part The following Kubernetes components are directly scraped by Prometheus: - kubelet* -- ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -231,11 +231,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -244,6 +244,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **etcd:** The internal Kubernetes component that is the distributed key/value store which Kubernetes uses for persistent storage of all cluster information. - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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. 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 fb4a5c764c4..672109a43c6 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 @@ -205,13 +205,13 @@ Prometheus 从称为 [exporter](https://prometheus.io/docs/instrumenting/exporte Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* -- ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -227,11 +227,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -240,6 +240,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **etcd**：Kubernetes 内部组件，它是 Kubernetes 用于持久存储所有集群信息的分布式键/值存储。 - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 -- **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 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 2dbd49f42d2..02efc616f00 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 @@ -206,12 +206,13 @@ Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* - ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -228,10 +229,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | | ingress-nginx* | 收集 kubelet 直接公开的指标，由 rkeIngressNginx.enabled 公开 | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -241,5 +243,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 - **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 2dbd49f42d2..02efc616f00 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -206,12 +206,13 @@ Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* - ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -228,10 +229,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | | ingress-nginx* | 收集 kubelet 直接公开的指标，由 rkeIngressNginx.enabled 公开 | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE 和 RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -241,5 +243,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 - **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index fb4a5c764c4..672109a43c6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -205,13 +205,13 @@ Prometheus 从称为 [exporter](https://prometheus.io/docs/instrumenting/exporte Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* -- ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -227,11 +227,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -240,6 +240,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **etcd**：Kubernetes 内部组件，它是 Kubernetes 用于持久存储所有集群信息的分布式键/值存储。 - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 -- **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index fb4a5c764c4..672109a43c6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -205,13 +205,13 @@ Prometheus 从称为 [exporter](https://prometheus.io/docs/instrumenting/exporte Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* -- ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -227,11 +227,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -240,6 +240,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **etcd**：Kubernetes 内部组件，它是 Kubernetes 用于持久存储所有集群信息的分布式键/值存储。 - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 -- **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index fb4a5c764c4..672109a43c6 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -205,13 +205,13 @@ Prometheus 从称为 [exporter](https://prometheus.io/docs/instrumenting/exporte Prometheus 直接抓取以下 Kubernetes 组件： - kubelet\* -- ingress-nginx\*\* +- Traefik\*\* - coreDns/kubeDns - kube-api-server \* 你可以选择通过 `hardenedKubelet.enabled` 来使用 PushProx，但这不是默认设置。 -\*\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\*\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 基于 Kubernetes 发行版抓取指标 @@ -227,11 +227,11 @@ Prometheus 直接抓取以下 Kubernetes 组件： | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | 不可用 | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | 收集 kubelet 直接公开的指标 | -| ingress-nginx* | 收集 kubelet 直接公开的指标，由 rke2IngressNginx.enabled 公开 | 不可用 | 不可用 | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | 收集 coreDns/kubeDns 直接公开的指标 | | kube-api-server | 收集 kube-api-server 直接公开的指标 | 收集 kube-appi-server 直接公开的指标 | 收集 kube-api-server 直接公开的指标 | -\* RKE2 集群默认部署 ingress-nginx，并将其视为内部 Kubernetes 组件。 +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### 名词解释 @@ -240,6 +240,6 @@ Prometheus 直接抓取以下 Kubernetes 组件： - **etcd**：Kubernetes 内部组件，它是 Kubernetes 用于持久存储所有集群信息的分布式键/值存储。 - **kube-proxy**：内部 Kubernetes 组件，用于监控 API server 的 pod/service 更改以保持网络最新状态。 - **kubelet**：内部 Kubernetes 组件，用于为 pod 监视节点上的 API server 并确保这些 pod 能运行。 -- **ingress-nginx**：用于 Kubernetes 的 Ingress controller，使用 NGINX 作为反向代理和负载均衡器。 +- **Traefik:** An Ingress controller for Kubernetes that can be used as a reverse proxy and load balancer. - **coreDns/kubeDns**：负责 DNS 的内部 Kubernetes 组件。 - **kube-api-server**：负责为其他 master 组件公开 API 的主要内部 Kubernetes 组件。 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 514c1828af9..6679d764de6 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 @@ -211,12 +211,13 @@ The following Kubernetes components are directly scraped by Prometheus: - kubelet* - ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -233,10 +234,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | | ingress-nginx* | Collects metrics directly exposed by kubelet, exposed by rkeIngressNginx.enabled | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server |Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -246,5 +248,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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. diff --git a/versioned_docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 514c1828af9..6679d764de6 100644 --- a/versioned_docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.11/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -211,12 +211,13 @@ The following Kubernetes components are directly scraped by Prometheus: - kubelet* - ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -233,10 +234,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | kube-proxy | rkeProxy.enabled | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | | ingress-nginx* | Collects metrics directly exposed by kubelet, exposed by rkeIngressNginx.enabled | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server |Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE and RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -246,5 +248,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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. diff --git a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 1a34415ea58..99c7c066cfd 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -210,13 +210,13 @@ Certain internal Kubernetes components are scraped via a proxy deployed as part The following Kubernetes components are directly scraped by Prometheus: - kubelet* -- ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -231,11 +231,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -244,6 +244,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **etcd:** The internal Kubernetes component that is the distributed key/value store which Kubernetes uses for persistent storage of all cluster information. - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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. diff --git a/versioned_docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 1a34415ea58..99c7c066cfd 100644 --- a/versioned_docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.13/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -210,13 +210,13 @@ Certain internal Kubernetes components are scraped via a proxy deployed as part The following Kubernetes components are directly scraped by Prometheus: - kubelet* -- ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -231,11 +231,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -244,6 +244,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **etcd:** The internal Kubernetes component that is the distributed key/value store which Kubernetes uses for persistent storage of all cluster information. - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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. diff --git a/versioned_docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md b/versioned_docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md index 1a34415ea58..99c7c066cfd 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md @@ -210,13 +210,13 @@ Certain internal Kubernetes components are scraped via a proxy deployed as part The following Kubernetes components are directly scraped by Prometheus: - kubelet* -- ingress-nginx** +- Traefik** - coreDns/kubeDns - kube-api-server \* You can optionally use `hardenedKubelet.enabled` to use a PushProx, but that is not the default. -** For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +** For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Scraping Metrics Based on Kubernetes Distribution @@ -231,11 +231,11 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w | etcd | rke2Etcd.enabled | kubeAdmEtcd.enabled | Not available | | kube-proxy | rke2Proxy.enabled | kubeAdmProxy.enabled | k3sServer.enabled | | kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | Collects metrics directly exposed by kubelet | -| ingress-nginx* | Collects metrics directly exposed by kubelet, Exposed by rke2IngressNginx.enabled | Not available | Not available | +| Traefik* | Collects metrics directly exposed by kubelet | Not available | Not available | | coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | Collects metrics directly exposed by coreDns/kubeDns | | kube-api-server | Collects metrics directly exposed by kube-api-server | Collects metrics directly exposed by kube-appi-server | Collects metrics directly exposed by kube-api-server | -\* For RKE2 clusters, ingress-nginx is deployed by default and treated as an internal Kubernetes component. +\* For RKE2 clusters, Traefik is deployed by default and treated as an internal Kubernetes component. ### Terminology @@ -244,6 +244,6 @@ Metrics are scraped differently based on the Kubernetes distribution. For help w - **etcd:** The internal Kubernetes component that is the distributed key/value store which Kubernetes uses for persistent storage of all cluster information. - **kube-proxy:** The internal Kubernetes component that watches the API server for pods/services changes in order to maintain the network up to date. - **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. +- **Traefik:** An Ingress controller for Kubernetes that can be used 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.