Hi team, I need help with a Rancher 2.14.x login issue on our management cluster. Environment: - Rancher: upgraded from v2.14.2 to v2.14.3 - Helm chart: rancher-2.14.3 - Kubernetes: k3s v1.34.8+k3s1 - Helm client: v3.21.2 Problem: The Rancher UI login still fails after entering valid admin credentials. Browser/network shows the failing API as: POST /v1/ext.cattle.io.selfuser HTTP 404 What I verified: 1. Rancher backend login works: - POST /v3-public/localProviders/local?action=login returns HTTP 201 - Token is successfully generated 2. The selfuser endpoint fails: - POST /v1/ext.cattle.io.selfuser returns HTTP 404 - This happens even when port-forwarding directly to the Rancher pod, so it does not look like browser, ingress, service, or port-forward routing issue. 3. Kubernetes API aggregation for ext.cattle.io appears healthy: - APIService v1.ext.cattle.io is Available=True - kubectl get --raw /apis/ext.cattle.io/v1 lists selfusers - kubectl create SelfUser returns system:admin 4. metrics-server issue was also fixed: - v1beta1.metrics.k8s.io is now Available=True - kubectl top nodes works History: - Rancher v2.9.2 was installed earlier and login worked. - We removed that and installed Rancher v2.14.2. - v2.14.2 had the UI login issue. - We upgraded to v2.14.3, but the same /v1/ext.cattle.io.selfuser 404 remains. Current evidence: - Login API: HTTP 201 - Token generated successfully - /v1/ext.cattle.io.selfuser: HTTP 404 - /v1/schemas does not show ext.cattle.io resources - Direct Kubernetes ext.cattle.io SelfUser test works Question: Is this a known Rancher v2.14.3 issue with Kubernetes/k3s v1.34, or could this be stale state from the previous uninstall/reinstall/upgrade path? Is there a supported fix to make Rancher /v1 register ext.cattle.io.selfuser, or should we rebuild the Rancher management cluster cleanly?