---
name: openshift-ts-ingress-status
title: Checking the status of Ingress components
description: 'To check the overall health and status of your cluster''s Ingress components:'
last-updated: 2026-07-27
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/openshift?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Checking the status of Ingress components
{: #ingress-status}
{: support}

[Virtual Private Cloud]{: tag-vpc} [Classic infrastructure]{: tag-classic-inf}

## Getting the status and message
{: #check_status}

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

```sh
ibmcloud oc ingress status-report get -c CLUSTER_NAME_OR_ID
```
{: pre}

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

Example output




```sh
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
```
{: screen}







The **Ingress Status** and **Ingress Message** fields are also returned in the output of the `ibmcloud oc cluster get` command. 
{: tip}


## Ingress statuses
{: #ingress_status}

The Ingress Status reflects the overall health of the Ingress components.
{: shortdesc}

| 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. |
{: caption="Ingress statuses" caption-side="bottom"}


## Ingress messages
{: #ingress_message}

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.
{: shortdesc}

|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?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errionf&format=markdown).|
| `The Ingress Operator is in a degraded state (ERRIODEG).` | For more information, see [Why does the Ingress status show an ERRIODEG error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-erriodeg&format=markdown). |
| `One or more routes not admitted (ERRRNA).` | For more information, see [Why does the Ingress status show an ERRRNA error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errrna&format=markdown).|
| `The external service is missing (ERRESNF).` | For more information, see [Why does the Ingress status show an ERRESNF error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-erresnf&format=markdown).|
| `The service is missing one or more worker IPs (ERRSEIPM).` | For more information, see [Why does the Ingress status show an ERRSEIPM error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errseipm&format=markdown).|
| `The load balancer service address is missing (ERRSAM).` | For more information, see [Why does the Ingress status show an ERRSAM error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errsam&format=markdown).|
| `Could not access Secrets Manager instance (ESSSMI).` | For more information, see [Why does the Ingress status show an ESSSMI error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-esssmi&format=markdown).|
| `Could not access the secret group (ESSSMG).` | For more information, see [Why does the Ingress status show an ESSSMG error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-esssmg&format=markdown).|
| `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?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essvc&format=markdown).|
| `The certificate for TLS secret expired or will expire soon (ESSEC).` | For more information, see [Why does the Ingress status show an ESSEC error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essec&format=markdown).|
| `The Opaque secret field expired or will expire soon (ESSEF).` | For more information, see [Why does the Ingress status show an ESSEF error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essef&format=markdown).|
| `The secret status shows a warning (ESSWS).` | For more information, see [Why does the Ingress status show an ESSWS error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essws&format=markdown).|
| `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?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-essdne&format=markdown).|
| `The external provider for the given subdomain has authorization issues (ERRDSAISS).` | For more information, see [Why does the Ingress status show an ERRDSAISS error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errdsaiss&format=markdown)|
| `The subdomain has TLS secret issues (ERRDSISS).` | For more information, see [Why does the Ingress status show an ERRDSISS error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errdsiss&format=markdown).|
| `The subdomain has DNS resolution issues (ERRDRISS).` | For more information, see [Why does the Ingress status show an ERRDRISS error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errdriss&format=markdown).|
| `The subdomain has incorrect addresses registered (ERRDSIA).` | For more information, see [Why does the Ingress status show an ERRDSIA error?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-ingress-errdsia&format=markdown).|
{: caption="Ingress messages" caption-side="bottom"}