Good morning all! We're in the process of rolling out new Harbor registries. After updating the system-default-registry on the Rancher Mgmt side, and the Container Registry field for the downstream clusters (cluster config)... the running pods do not get restarted using the new registry. Even the restart of a node does not trigger it. I did find that adding a system-default-registry: registry.domain.com under machineSelectorConfig: does accomplish this for existing clusters. The issue is that newly deployed clusters are still using the old registry, even if its set to the new during the deployment. Rancher 2.9.2 - 2.11.1