public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 20:48:11 +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:09:19 -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-controlplane-nodes.md
+2 -2
View File
@@ -4,7 +4,7 @@ title: Troubleshooting Controlplane Nodes
This section applies to nodes with the `controlplane` role.
# Check if the Controlplane Containers are Running
## Check if the Controlplane Containers are Running
There are three specific containers launched on nodes with the `controlplane` role:
@@ -26,7 +26,7 @@ f3d287ca4549 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..."
bdf3898b8063 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kube-controller-manager
```
# Controlplane Container Logging
## Controlplane Container Logging
> **Note:** If you added multiple nodes with the `controlplane` role, both `kube-controller-manager` and `kube-scheduler` use a leader election process to determine the leader. Only the current leader will log the performed actions. See [Kubernetes leader election](../other-troubleshooting-tips/kubernetes-resources.md#kubernetes-leader-election) how to retrieve the current leader.
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.
versioned_docs/version-2.5/troubleshooting/kubernetes-components/troubleshooting-worker-nodes-and-generic-components.md
+2 -2
View File
@@ -4,7 +4,7 @@ title: Troubleshooting Worker Nodes and Generic Components
This section applies to every node as it includes components that run on nodes with any role.
# Check if the Containers are Running
## Check if the Containers are Running
There are two specific containers launched on nodes with the `worker` role:
@@ -24,7 +24,7 @@ CONTAINER ID IMAGE COMMAND
a30717ecfb55 rancher/hyperkube:v1.11.5-rancher1 "/opt/rke-tools/en..." 3 hours ago Up 3 hours kubelet
```
# Container Logging
## Container Logging
The logging of the containers can contain information on what the problem could be.