Hello! The problem is that, cattle-cluster-agent doesn’t use the extra settings i put in the .yaml file before kubectl deployment (dnsPolicy: Default and hostNetwork: true) after restarting. So it’ll run fine and show up in rancher, but then restart and be unable to find my rancher server, because it uses the wrong resolv.conf file.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Rancher Bug Advisory in v2.4.0: Rancher Issue #26339 - kubelets constantly restarting in user clusters | 1 | 3130 | March 31, 2020 | |
| New install of Rancher v2.5.1, cattle-cluster-agent can't resolve the Rancher host | 3 | 5558 | July 16, 2021 | |
| Having an issue --> cattle-cluster-agent in state CrashLoopBackOff | 3 | 2391 | October 30, 2020 | |
| After Rancher URL change, older rancher-agent pod restarting with wrong URL | 1 | 516 | December 20, 2023 | |
|
Cattle-cluster-agent
|
1 | 709 | August 19, 2021 |