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 | |
|---|---|---|---|---|
| Cluster Agent Pods Missing, Deployment Not Ready | 1 | 660 | February 16, 2022 | |
| Cattle-cluster-agent ERROR when importing cluster | 1 | 3756 | September 10, 2021 | |
| Rancher Bug Advisory in v2.4.0: Rancher Issue #26339 - kubelets constantly restarting in user clusters | 1 | 2945 | March 31, 2020 | |
| Kube-dns could not resolve anything (RKE Cluster) | 0 | 3981 | May 22, 2019 | |
| Cattle-cluster-agent can't bind to port 6443 | 14 | 3712 | March 4, 2021 |