This message was deleted.

I think that's the problem on Rancher 2.8.0, just try to restart the master one by one, check the CM and what is the logs. If possible just upgrade the rancher to the 2.11.2 with upgrade path to 2.9 respectively to 2.11.2. I have this situation before. BTW, please check the cluster containerd, is there already the latest or not. You can check in CM of the cluster then Edit Config