Harbor Deployment Pods Stuck in ImagePullBackOff
search cancel

Harbor Deployment Pods Stuck in ImagePullBackOff

book

Article ID: 393063

calendar_today

Updated On:

Products

VMware Tanzu Mission Control

Issue/Introduction

Harbor deployment pods are failing to pull images and stuck in ImagePullBackOff, and when attempting to login to the Harbor UI it fails with error "Core service is not available".

When describing the Harbor deployment the image reference line is still pointing the endpoint extensions.aws-usw2.tmc.cloud.vmware.com.

Environment

TKG clusters that Harbor was installed onto the clusters directly.

Cause

The Harbor deployment pods are failing to pull images because they are attempting to pull from the old decommissioned VMware image repo endpoint extensions.aws-usw2.tmc.cloud.vmware.com instead of the new Broadcom TMC image repo endpoint extensions.stacks.whitesand.tmc.tanzu.broadcom.com.  

Resolution

Please open a support case with Broadcom support under VMware Tanzu Mission Control to investigate this issue.