Hello Everyone anyone know how to fix this

root@xxxx ~ # kubectl exec -ti rancher-865f7d9454-7s6dt -n cattle-system reset-password
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
W0628 02:05:50.193004   14484 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
2 users were found with <http://authz.management.cattle.io/bootstrapping=admin-user|authz.management.cattle.io/bootstrapping=admin-user> label. They are [user-5wmpr user-nkh57]. Can only reset the default admin password when there is exactly one user with this label
command terminated with exit code 1

root@xxxx ~ # kubectl get user
NAME           AGE
u-6kh6x        26d
u-b4qkhsnliz   26d
u-mo773yttt4   26d
user-5wmpr     26d
user-nkh57     3d8h

kubectl --kubeconfig $KUBECONFIG -n cattle-system exec $(kubectl --kubeconfig $KUBECONFIG -n cattle-system get pods -l app=rancher | grep '1/1' | head -1 | awk '{ print $1 }') -- ensure-default-admin
W0628 02:04:17.855783   14514 client_config.go:617] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
Found existing default admin user (user-nkh57)
Existing default admin user (user-nkh57) is already enabled
Existing default admin user (user-nkh57) already labeled as admin
Existing default admin user (user-nkh57) is already an admin

is this for rancher desktop or a standard rancher deployment?

standard rancher deployment

so i would head over to the rancher channel as folks in this channel are focused on the rancher-desktop tool and the cluster management isn’t really there

okay, got it. Can you please tell me, in which channel should I ask

possibly rke?

okay thanks

I think #general is used for Rancher Manager for historical reasons (when this whole Slack instance was solely about it)