"Failed to pull image" (403 Forbidden) when deploying VIP Authentication Hub sample applications

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

When deploying a sample application in a Kubernetes cluster, the image pull for cadir pod fails with a 403 Forbidden error.

Failed to pull image "securityservices.packages.broadcom.com/cadir:4.0.1.1015": failed to resolve reference "securityservices.packages.broadcom.com/cadir:4.0.1.1015": unexpected status from HEAD request to https://securityservices.packages.broadcom.com/v2/cadir/manifests/4.0.1.1015: 403

Environment

Symantec Identity Security Platform (IDSP) / VIP Authentication Hub 4.0.x

Cause

The error occurs due to an incorrect Helm configuration parameter for the image pull secret. Using the global.ssp.registry.existingSecrets parameter instead of the required global.registry.existingSecrets parameter prevents the cluster from correctly authenticating with the Broadcom package registry

Resolution

To resolve the image pull failure, update your Helm deployment command to use the correct global registry secret parameter.

Incorrect Parameter: --set global.ssp.registry.existingSecrets[0].name=ssp-registrypullsecret

Correct Parameter: --set global.registry.existingSecrets[0].name=ssp-registrypullsecret