Error: ImagePullBackOff for platform-consumption-operator pod in Tanzu Hub
search cancel

Error: ImagePullBackOff for platform-consumption-operator pod in Tanzu Hub

book

Article ID: 445770

calendar_today

Updated On:

Products

VMware Tanzu Platform Core VMware Tanzu Platform - Hub

Issue/Introduction

Operator is attempting to connect a cluster as detailed in Tanzu Hub: Connect and manage a Connected Cluster.
 
At the step of updating Administration > Connected Clusters after installing the provided yaml to the cluster, an image pull backoff occurs for for the platform-consumption-operator-controller-manager pod. The response status is 403 indicating unauthorized:
 
kubectl describe pod platform-consumption-operator-controller-manager-n tanzusm 
   state:
      waiting:
        message: 'Back-off pulling image "tanzu-platform-content.packages.broadcom.com/containers/tanzusm/prd/platform-consumption-operator:10.4.2":
          ErrImagePull: failed to pull and unpack image "tanzu-platform-content.packages.broadcom.com/containers/tanzusm/prd/platform-consumption-operator:10.4.2":
          failed to resolve image: unexpected status from HEAD request to https://tanzu-platform-content.packages.broadcom.com/v2/containers/tanzusm/prd/platform-consumption-operator/manifests/10.4.2:
          403 '
        reason: ImagePullBackOff

Environment

Tanzu Hub 10.4

Cause

This problem will occur if the secret is not set correctly within the Broadcom registry token.

Resolution

The solution is to perform the steps Create the image pull secret as outlined in Broadom techdocs.

The steps are as follows:

  1. Create namespace
  2. Create secret
    • Docker-server: “https://tanzu-platform-content.packages.broadcom.com”
    • Docker-username: your Broadcom support email address.
    • Docker-password: generate a token from https://support.broadcom.com/group/ecx/registry-token 
    • For demos you can configure the secret so that images are pulled directly from Broadcom
    • See docs here on to how to configure to use your own OCI registry
  3. Verify connector status is online
    • Hub > Administration > Connected Cluster