Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove extra image captions #1576

Merged
merged 2 commits into from
Nov 25, 2024
Merged

Remove extra image captions #1576

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0b1a9b0
Remove duplicate image caption
btat Nov 20, 2024
8bf8fef
Remove figcaption that has no associated image
btat Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions docs/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...current/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...on-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...ion-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...ion-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...ion-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,5 @@ Rancher Server 的数据存储在 etcd 中。etcd 数据库可以在所有三个
- Ingress Controller 会把 HTTP 重定向到 HTTPS，在 TCP/443 端口终结 SSL/TLS。
- Ingress Controller 会把流量转发到 Rancher deployment 的 Pod 上的 TCP/80 端口。

<figcaption>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止：</figcaption>

![Rancher 的高可用 Kubernetes 安装](/img/ha/rancher2ha.svg)
<sup>使用 4 层负载均衡器在 Kubernetes 集群中安装 Rancher：Ingress Controller 的 SSL 终止</sup>
3 changes: 0 additions & 3 deletions ...ion-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,9 +56,6 @@ PrometheusRule 用于定义指标或时间序列数据库查询触发告警的

- 路由和接收器也通过 Alertmanager Secret 存储在 Kubernetes API 中。当 Secret 更新时，Alertmanager 也会自动更新。请注意，路由仅通过标签发生（而不是通过注释等）。

<figcaption>数据如何流经 Monitoring 应用程序</figcaption>


## 2. Prometheus 的工作原理

### 存储时间序列数据
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions ...on-2.10/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
3 changes: 0 additions & 3 deletions ...nations/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions ...ion-2.6/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions ...ion-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions ...ion-2.8/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down
2 changes: 0 additions & 2 deletions ...o-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>

![High-availability Kubernetes Installation of Rancher](/img/ha/rancher2ha.svg)
<sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>
3 changes: 0 additions & 3 deletions ...ion-2.9/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.).

<figcaption>How data flows through the monitoring application:</figcaption>


## 2. How Prometheus Works

### Storing Time Series Data
Expand Down