When attempting to deploy or fetch packages, the operation fails with an I/O timeout. This typically occurs when the environment is still configured to use the deprecated VMware or interim Broadcom URLs.
[ timestamp ] <-- dial tcp ##.##.##.##:443: i/o timeout GET https://extensions.aws-usw2.tmc.cloud.vmware.com
imgpkg: Error: Fetching image:
Error while preparing a transport to talk with the registry:
Unable to create round tripper:
Get "https://extensions.aws-usw2.tmc.cloud.vmware.com/v2/": dial tcp ##.##.##.##:443: i/o timeout
OR
[ timestamp ] <-- dial tcp ##.##.##.##:443: i/o timeout GET https://extensions.stacks.whitesand.tmc.tanzu.broadcom.com/v2/
imgpkg: Error: Fetching image:
Error while preparing a transport to talk with the registry:
Unable to create round tripper:
Get "https://extensions.stacks.whitesand.tmc.tanzu.broadcom.com/v2/": dial tcp ##.##.##.##:443: i/o timeout
As part of a planned infrastructure migration, legacy package repositories have reached their scheduled End of Life (EOL) to align with the final TMC SaaS cutover.
Replace the old registry URL with the following: projects.packages.broadcom.com/vsphere/tmc-sm/standard/repo/<version>:<version>
For more details, refer: Copying Tanzu Standard and Inspection Images
Since the TMC SaaS has been decommissioned, so the images have been removed.
The TMC package repo extensions.stacks.blacksea.tmc.tanzu.broadcom.com/packages/standard/repo/v2025.6.18:v2025.6.18 can be replaced by projects.packages.broadcom.com/vsphere/tmc-sm/standard/repo/v2025.6.18:v2025.6.18