New downstream clusters are picking up the old default registry, even though the system default registry has been modified.

This document (000021906) is provided subject to the disclaimer at the end of this document.

Environment

RKE2

RKE

Situation

The system default registry, configured via the Rancher UI's Global Settings, is not being applied to new downstream clusters. These clusters are still attempting to pull images from the old registry

Resolution

The system default registry, configured via the Rancher UI's Global Settings, is not being applied to new downstream clusters.

These clusters are still attempting to pull images from the old registry

Rancher UI > Explore Local cluster > Rancher deployment > Edit YML

Take a backup of the below YAML before the edit

Rancher UI > Explore Local cluster > Rancher deployment > Edit YML > Update and Save

Perform the Rancher pod rollout restart.

Rancher UI > Explore Local cluster > Rancher deployment > Redeploy

Cause

While creating a new downstream cluster through Rancher, Rancher acts as an orchestrator. It uses its internal configuration, including the default registry, to provision the cluster's control plane and worker nodes. If Rancher tries to pull cattle-cluster-agent, Kubernetes components, CNI plugins, or other essential images from the wrong registry, the cluster creation will fail or result in an unhealthy state.

Status

Top Issue

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.