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

fixed other-troubleshooting-tips/registered-clusters.md

Browse Source
This commit is contained in:
martyav
2024-09-19 12:41:31 -04:00
parent 9c3281e07e
commit 21ec1b7320
4 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.7/troubleshooting/other-troubleshooting-tips/registered-clusters.md
+3 -3
View File
@@ -10,13 +10,13 @@ The commands/steps listed on this page can be used to check clusters that you ar
Make sure you configured the correct kubeconfig (for example, `export KUBECONFIG=$PWD/kubeconfig_from_imported_cluster.yml`)
### Rancher agents
## Rancher Agents
Communication to the cluster (Kubernetes API via cattle-cluster-agent) and communication to the nodes is done through Rancher agents.
If the cattle-cluster-agent cannot connect to the configured `server-url`, the cluster will remain in **Pending** state, showing `Waiting for full cluster configuration`.
#### cattle-node-agent
### cattle-node-agent
:::note
@@ -49,7 +49,7 @@ Check logging of a specific cattle-node-agent pod or all cattle-node-agent pods:
kubectl -n cattle-system logs -l app=cattle-agent
```
#### cattle-cluster-agent
### cattle-cluster-agent
Check if the cattle-cluster-agent pod is present in the cluster, has status **Running** and doesn't have a high count of Restarts: