SSP platform shows unhealthy as cluster-api pod status stuck at InvalidImage name

Products

• VMware vDefend Firewall with Advanced Threat Prevention
• VMware vDefend Firewall

Issue/Introduction

 You will observe in SSPi diagnostic screen with unhealthy status of namespace nsxi-platform because cluster-api pod is failing with InvalidImage name error.

 

Environment

SSP 5.0

Cause

The container image name in cluster-api pod's YAML manifest is invalid.

Resolution

Below command will give the cluster-api pods status details.

1. k get pod -A | grep cluster
nsxi-platform cluster-api-7d59fbf57c-hn7xv                            1/2 ErrImagePull 0 8s
nsxi-platform cluster- -cbf8d68-dq2zh                                 1/2 InvalidImageName 0 13m
   2. Examine the events of the cluster-api pod to review the events :

k describe pod cluster-api-XXX -n nsxi-platform

We will see below error,  The error message "invalid reference format" indicates an issue with the image name provided in the pod specification. The presence of the equals sign (=) at the beginning of the hostname (=.xx.yyy.com.my) is likely the cause or the complete name is missing.

Warning  InspectFailed  80s (x85191 over 12d)  kubelet  Failed to apply default image tag "=.xx.yyy.com.my/clustering/cluster_api@sha256:dd1ae909951b5434cae59c722ce422fe032b8b19ec14ee2ba1acbd01dcffc472": couldn't parse image name "=.xx.yyy.com.my/clustering/cluster_api@sha256:dd1ae909951b5434cae59c722ce422fe032b8b19ec14ee2ba1acbd01dcffc472": invalid reference format

where xx.yyy.com.my should match SSPI FQDN

   

   3. If we see any error related to incorrect image name, please contact Broadcom support for further assistance