This is a summary and hopefully it helps someone else.
We run lab rancher and prod rancher instances in their own tiny AWS EKS clusters. We recently updated to 2.13.2 and bumped up the instance types on prod rancher to c8a. Rancher is snappy. Users are happy. Rancher Fleet performance is much better.
When I went to update our clusters from eks 1.32 to 1.33 i noticed that for the most part i couldn't see the config of most of my clusters across both Rancher instances. I panicked and began investigating. After searching around a bit I found a solution: Go to
https://rancher.rancher-eks01.c.pfcld.com/v1/userpreferences. and deleted my user preferences. logout of rancher and login again. If that doesn't fix it then got to Chrome developer tools->application tab (top)->storage tab (left) and click the "clear site data" button. 💥 Things are working and i can see my cluster configs.
Fast forward a couple of days and I'm back upgrading more clusters. Login to my prod Rancher and can't see configs (can see nodes and other cluster bits but not the config page). Try the above "solution" and got no improvement.
After a bit of searching I found this: In Rancher i go to Global Settings > Feature Flags, search for ui-sql-cache and disable it.
This restarts Rancher. but again 💥 I can see my cluster configs.