The Grafana Secret is only used once during the initialization to seed the database. From there on, Grafana will look into the database to fetch the admin password. Maybe the Grafana secret in Kubernetes was deleted somehow (re-installation?), so it was re-created by UMH? As this would not overwrite the database, it could be the cause that you still need the old password.