public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-26 04:58:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1576 from btat/img-caption

Browse Source 
Remove extra image captions
This commit is contained in:
Billy Tat
2024-11-25 11:19:24 -08:00
committed by GitHub
parent 7838a690ed 8bf8fef3ba
commit 48c191e1b6
27 changed files with 0 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.7/how-to-guides/new-user-guides/kubernetes-cluster-setup/high-availability-installs.md
-2
View File
@@ -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>
versioned_docs/version-2.7/integrations-in-rancher/monitoring-and-alerting/how-monitoring-works.md
-3
View File
@@ -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