Fix links and formatting

2026-09-25 12:38:05 +00:00 · 2022-09-15 17:48:58 +08:00
parent 5a3bfa4271
commit 6f187bee01
31 changed files with 47 additions and 2 deletions
@@ -77,4 +77,5 @@ The storage controller and replicas are themselves orchestrated using Kubernetes
 You can learn more about its architecture [here.](https://longhorn.io/docs/1.0.2/concepts/)

 <figcaption>Longhorn Architecture</figcaption>
+
 ![Longhorn Architecture](/img/longhorn-architecture.svg)
@@ -40,6 +40,7 @@ To see the Alertmanager UI, go to the **Cluster Explorer.** In the top left corn
 **Result:** The Alertmanager UI opens in a new tab. For help with configuration, refer to the [official Alertmanager documentation.](https://prometheus.io/docs/alerting/latest/alertmanager/)

 <figcaption>The Alertmanager UI</figcaption>
+
 ![Alertmanager UI](/img/alertmanager-ui.png)


@@ -65,6 +66,7 @@ To see what services you are monitoring, you will need to see your targets. Targ
 To see the Prometheus Targets, install `rancher-monitoring`. Then go to the **Cluster Explorer.** In the top left corner, click **Cluster Explorer > Monitoring.** Then click **Prometheus Targets.**

 <figcaption>Targets in the Prometheus UI</figcaption>
+
 ![Prometheus Targets UI](/img/prometheus-targets-ui.png)

 ### Viewing the PrometheusRules
@@ -76,4 +78,5 @@ To see the PrometheusRules, install `rancher-monitoring`. Then go to the **Clust
 You can also see the rules in the Prometheus UI:

 <figcaption>Rules in the Prometheus UI</figcaption>
+
 ![PrometheusRules UI](/img/prometheus-rules-ui.png)
@@ -163,7 +163,9 @@ However, users can choose to log in to Grafana as an [Admin](https://grafana.com
 To see the Grafana UI, install `rancher-monitoring`. Then go to the **Cluster Explorer.** In the top left corner, click **Cluster Explorer > Monitoring.** Then click **Grafana.

 <figcaption>Cluster Compute Resources Dashboard in Grafana</figcaption>
+
 ![Cluster Compute Resources Dashboard in Grafana](/img/cluster-compute-resources-dashboard.png)

 <figcaption>Default Dashboards in Grafana</figcaption>
+
 ![Default Dashboards in Grafana](/img/grafana-default-dashboard.png)
@@ -12,6 +12,7 @@ In a standard Kubernetes deployment, resource quotas are applied to individual n
 In the following diagram, a Kubernetes administrator is trying to enforce a resource quota without Rancher. The administrator wants to apply a resource quota that sets the same CPU and memory limit to every namespace in his cluster (`Namespace 1-4`) . However, in the base version of Kubernetes, each namespace requires a unique resource quota. The administrator has to create four different resource quotas that have the same specs configured (`Resource Quota 1-4`) and apply them individually.

 <sup>Base Kubernetes: Unique Resource Quotas Being Applied to Each Namespace</sup>
+
 ![Native Kubernetes Resource Quota Implementation](/img/kubernetes-resource-quota.svg)

 Resource quotas are a little different in Rancher. In Rancher, you apply a resource quota to the project, and then the quota propagates to each namespace, whereafter Kubernetes enforces your limits using the native version of resource quotas. If you want to change the quota for a specific namespace, you can override it.
@@ -30,6 +31,7 @@ The resource quota includes two limits, which you set while creating or editing
 In the following diagram, a Rancher administrator wants to apply a resource quota that sets the same CPU and memory limit for every namespace in their project (`Namespace 1-4`). However, in Rancher, the administrator can set a resource quota for the project (`Project Resource Quota`) rather than individual namespaces. This quota includes resource limits for both the entire project (`Project Limit`) and individual namespaces (`Namespace Default Limit`). Rancher then propagates the `Namespace Default Limit` quotas to each namespace (`Namespace Resource Quota`) when created.

 <sup>Rancher: Resource Quotas Propagating to Each Namespace</sup>
+
 ![Rancher Resource Quota Implementation](/img/rancher-resource-quota.png)

 Let's highlight some more nuanced functionality. If a quota is deleted at the project level, it will also be removed from all namespaces contained within that project, despite any overrides that may exist. Further, updating an existing namespace default limit for a quota at the project level will not result in that value being propagated to existing namespaces in the project; the updated value will only be applied to newly created namespaces in that project. To update a namespace default limit for existing namespaces you can delete and subsequently recreate the quota at the project level with the new default value. This will result in the new default value being applied to all existing namespaces in the project.
@@ -10,6 +10,7 @@ Although the **Namespace Default Limit** propagates from the project to each nam
 In the diagram below, the Rancher administrator has a resource quota in effect for their project. However, the administrator wants to override the namespace limits for `Namespace 3` so that it has more resources available. Therefore, the administrator [raises the namespace limits](../../manage-clusters/projects-and-namespaces.md) for `Namespace 3` so that the namespace can access more resources.

 <sup>Namespace Default Limit Override</sup>
+
 ![Namespace Default Limit Override](/img/rancher-resource-quota-override.svg)

 How to: [Editing Namespace Resource Quotas](../../manage-clusters/projects-and-namespaces.md)
@@ -31,6 +31,7 @@ After installing NGINX, you need to update the NGINX configuration file, `nginx.
    > **Note:** See [NGINX Documentation: TCP and UDP Load Balancing](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/) for all configuration options.

    <figcaption>Example NGINX config</figcaption>
+    
    ```
    worker_processes 4;
    worker_rlimit_nofile 40000;
@@ -23,5 +23,6 @@ For information on how Rancher works, regardless of the installation method, ref
 - 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>
@@ -28,6 +28,7 @@ We don't recommend installing Rancher in a single Docker container, because if t
 One option for the underlying Kubernetes cluster is to use K3s Kubernetes. K3s is Rancher's CNCF certified Kubernetes distribution. It is easy to install and uses half the memory of Kubernetes, all in a binary of less than 100 MB. Another advantage of K3s is that it allows an external datastore to hold the cluster data, allowing the K3s server nodes to be treated as ephemeral.

 <figcaption>Architecture of a K3s Kubernetes Cluster Running the Rancher Management Server</figcaption>
+
 ![Architecture of a K3s Kubernetes Cluster Running the Rancher Management Server](/img/k3s-server-storage.svg)

 ### RKE Kubernetes Cluster Installations
@@ -35,6 +36,7 @@ One option for the underlying Kubernetes cluster is to use K3s Kubernetes. K3s i
 In an RKE installation, the cluster data is replicated on each of three etcd nodes in the cluster, providing redundancy and data duplication in case one of the nodes fails.

 <figcaption>Architecture of an RKE Kubernetes Cluster Running the Rancher Management Server</figcaption>
+
 ![Architecture of an RKE Kubernetes cluster running the Rancher management server](/img/rke-server-storage.svg)

 # Recommended Load Balancer Configuration for Kubernetes Installations
@@ -47,6 +49,7 @@ We recommend the following configurations for the load balancer and Ingress cont
 * The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment.

 <figcaption>Rancher installed on a Kubernetes cluster with layer 4 load balancer, depicting SSL termination at Ingress controllers</figcaption>
+
 ![Rancher HA](/img/ha/rancher2ha.svg)

 # Environment for Kubernetes Installations