Asking for help? Comment out what you need so we can get more information to help you!
Kubernetes version:client 1.12 , server 1.15
Rancher version: v2.3.1
Cloud being used: (put bare-metal if not on a public cloud) ON PREMISES
Installation method: Manual
Host OS: redhat enterprise 7.6
CNI and version: Canal
CRI and version: docker 19.03.5
i wasn’t able to copy paste the yaml file .
You can format your yaml by highlighting it and pressing Ctrl-Shift-C, it will make your output easier to read.
we have 9 VMs nodes and 6 physical nodes all part of kubernetes cluster. it happens sometimes that the cattle-node-agent and Canal system pod status gets to unavailable on one of the physical nodes , it get stuck until we delete the system pods to get recreated.
what could be the problem that can cause such behavior