TMC managed Supervisor clusters might be impacted by this.
The image repos for TMC were migrated starting January 31st according to the this KB. This led to some images not being updated.
Please contact Broadcom support if you see the incorrect image registry listed for the vsphere-resource-retreiver pod so the TMC team can correct this.
If an immediate workaround is required, edit the vsphere-resource-retriever deployment in the Supervisor cluster to manually point the image base URL to: extensions.stacks.whitesand.tmc.tanzu.broadcom.com
Example:
imageID: extensions.aws-usw2.tmc.cloud.vmware.com/extensions/resource-retriever/server@sha256:43b56e8f5876c130e21e097593b8e944395dad1176928e3e5274af111838d108
Becomes:
imageID: extensions.stacks.whitesand.tmc.tanzu.broadcom.com/extensions/resource-retriever/server@sha256:43b56e8f5876c130e21e097593b8e944395dad1176928e3e5274af111838d108