What did you expect to happen:
Templates should be updated to reflect their new host.
Anything else you would like to add:
Example error:
Warning Failed 5m28s kubelet Failed to pull image "gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.2.0": failed to pull and unpack image "gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.2.0": failed to resolve reference "gcr.io/cloud-provider-vsphere/csi/release/syncer:v3.2.0": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://gcr.io/v2/token?scope=repository%3Acloud-provider-vsphere%2Fcsi%2Frelease%2Fsyncer%3Apull&service=gcr.io: 401 Unauthorized
/kind bug
What steps did you take and what happened: Setting up a new cluster results in many pod failures since the images pointing to gcr.io/cloud-provider-vsphere are no longer available. https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/blob/f53e882349b500d13ddaf8055471f4458711e616/templates/cluster-template.yaml#L805
What did you expect to happen: Templates should be updated to reflect their new host.
Anything else you would like to add: Example error:
Linked issue: https://github.com/kubernetes-sigs/vsphere-csi-driver/issues/3053