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

fixed other-troubleshooting-tips/rancher-ha.md

Browse Source
This commit is contained in:
martyav
2024-09-17 17:31:27 -04:00
parent 4a6721f6ab
commit e6ffc6456c
7 changed files with 52 additions and 52 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/rancher-ha.md
+7 -7
View File
@@ -10,7 +10,7 @@ The commands/steps listed on this page can be used to check your Rancher Kuberne
Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kube_config_cluster.yml`).
### Check Rancher pods
## Check Rancher Pods
Rancher pods are deployed as a Deployment in the `cattle-system` namespace.
@@ -31,25 +31,25 @@ rancher-7dbd7875f7-qw7wb 1/1 Running 0 8m x.x.x.x x.x.x.
If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events.
#### Pod details
### Pod Details
```
kubectl -n cattle-system describe pods -l app=rancher
```
#### Pod container logs
### Pod Container Logs
```
kubectl -n cattle-system logs -l app=rancher
```
#### Namespace events
### Namespace Events
```
kubectl -n cattle-system get events
```
### Check ingress
## Check Ingress
Ingress should have the correct `HOSTS` (showing the configured FQDN) and `ADDRESS` (host address(es) it will be routed to).
@@ -64,7 +64,7 @@ NAME HOSTS ADDRESS PORTS AGE
rancher rancher.yourdomain.com x.x.x.x,x.x.x.x,x.x.x.x 80, 443 2m
```
### Check ingress controller logs
## Check Ingress Controller Logs
When accessing your configured Rancher FQDN does not show you the UI, check the ingress controller logging to see what happens when you try to access Rancher:
@@ -72,7 +72,7 @@ When accessing your configured Rancher FQDN does not show you the UI, check the
kubectl -n ingress-nginx logs -l app=ingress-nginx
```
### Leader election
## Leader Election
The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`).