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

Convert h1 to h2 (2.5)

Browse Source
This commit is contained in:
Billy Tat
2022-10-28 17:08:01 -07:00
parent 15a1e067a6
commit bb76e99d20
87 changed files with 319 additions and 336 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/troubleshooting/kubernetes-components/troubleshooting-nginx-proxy.md
+3 -3
View File
@@ -4,7 +4,7 @@ title: Troubleshooting nginx-proxy
The `nginx-proxy` container is deployed on every node that does not have the `controlplane` role. It provides access to all the nodes with the `controlplane` role by dynamically generating the NGINX configuration based on available nodes with the `controlplane` role.
# Check if the Container is Running
## Check if the Container is Running
The container is called `nginx-proxy` and should have status `Up`. The duration shown after `Up` is the time the container has been running.
@@ -20,7 +20,7 @@ CONTAINER ID IMAGE COMMAND CREATED
c3e933687c0e rancher/rke-tools:v0.1.15 "nginx-proxy CP_HO..." 3 hours ago Up 3 hours nginx-proxy
```
# Check Generated NGINX Configuration
## Check Generated NGINX Configuration
The generated configuration should include the IP addresses of the nodes with the `controlplane` role. The configuration can be checked using the following command:
@@ -59,7 +59,7 @@ stream {
}
```
# nginx-proxy Container Logging
## nginx-proxy Container Logging
The logging of the containers can contain information on what the problem could be.