This message was deleted.

Hey 👋 Wait... You have a k3d cluster running for 1 year? That's cool 🙂 You can `k3d cluster stop`/`k3d cluster start` to reload the registries config file since it's only evaluated at startup.

Thanks. I'm still getting an issue. I found out that the registries file is actually in the server node of the cluster. However there was still a file in /etc/rancher/k3s that was a "copy" of my registries file but with the old credentials.