IBM Cloud Docs
Checking the status of Ingress components

Checking the status of Ingress components

Virtual Private Cloud Classic infrastructure

Getting the status and message

To check the overall health and status of your cluster's Ingress components:

ibmcloud oc ingress status-report get -c <cluster_name_or_ID>

The state of the Ingress components are reported in an Ingress Status and Ingress Message.

Example output

Ingress Status:   healthy
Message:          All Ingress components are healthy.

Cluster            Status
ingress-operator   healthy
route-admission    healthy

Subdomain                                                                           Status
example-ae7743ca70a399d9cff4eaf617434c72-0000.us-south.containers.appdomain.cloud   healthy

Router           Status
router-default   healthy

Secret                                          Namespace           Status
example-ae7743ca70a399d9cff4eaf617434c72-0000   ibm-cert-store      healthy
example-ae7743ca70a399d9cff4eaf617434c72-0000   openshift-ingress   healthy

The Ingress Status and Ingress Message fields are also returned in the output of the ibmcloud oc cluster get command.

Ingress statuses

The Ingress Status reflects the overall health of the Ingress components.

Ingress statuses
Ingress status Description
healthy The Ingress components are healthy.
warning Some Ingress components might not function properly.
critical Some Ingress components are malfunctioning.
disabled Ingress status reporting is disabled. You can turn it on using the ibmcloud oc ingress status-report enable command.
unsupported Ingress status reporting is not available for unsupported cluster versions.
unknown The system is unable to calculate the Ingress status.

Ingress messages

The Ingress message provides details of what operation is in progress or information about any components that are unhealthy. Each status and message is described in the following tables.

Ingress messages
Ingress message Description
The Ingress Operator is missing from the cluster. (ERRIONF). For more information, see Why does the Ingress status show an ERRIONF error?.
The Ingress Operator is in a degraded state (ERRIODEG). For more information, see Why does the Ingress status show an ERRIODEG error?.
One or more routes not admitted (ERRRNA). For more information, see Why does the Ingress status show an ERRRNA error?.
The external service is missing (ERRESNF). For more information, see Why does the Ingress status show an ERRESNF error?.
The service is missing one or more worker IPs (ERRSEIPM). For more information, see Why does the Ingress status show an ERRSEIPM error?.
The load balancer service address is missing (ERRSAM). For more information, see Why does the Ingress status show an ERRSAM error?.
Could not access Secrets Manager instance (ESSSMI). For more information, see Why does the Ingress status show an ESSSMI error?.
Could not access the secret group (ESSSMG). For more information, see Why does the Ingress status show an ESSSMG error?.
The CRN does not match the default secret with the same domain (ESSVC). For more information, see Why does the Ingress status show an ESSVC error?.
The certificate for TLS secret expired or will expire soon (ESSEC). For more information, see Why does the Ingress status show an ESSEC error?.
The Opaque secret field expired or will expire soon (ESSEF). For more information, see Why does the Ingress status show an ESSEF error?.
The secret status shows a warning (ESSWS). For more information, see Why does the Ingress status show an ESSWS error?.
The secret is not present on the cluster or is in the wrong namespace (ESSDNE). For more information, see Why does the Ingress status show an ESSDNE error?.
The external provider for the given subdomain has authorization issues (ERRDSAISS). For more information, see Why does the Ingress status show an ERRDSAISS error?
The subdomain has TLS secret issues (ERRDSISS). For more information, see Why does the Ingress status show an ERRDSISS error?.
The subdomain has DNS resolution issues (ERRDRISS). For more information, see Why does the Ingress status show an ERRDRISS error?.
The subdomain has incorrect addresses registered (ERRDSIA). For more information, see Why does the Ingress status show an ERRDSIA error?.