This message was deleted.
# general
This message was deleted.
Looks like shutting down the Rancher server also causes a CPU usage drop, so Rancher is probably doing something that's blowing up that cluster.
So, finally discovered what was up. Turns out I had somehow put a User resource in the Rancher cluster into a weird state when doing the 2.6.7 Azure API transition. The user was being infinitely refreshed but never completing because, I guess, it had no UserAttribute resource. Nuking that user from the Rancher UI immediately quieted down all clusters.