---
name: openshift-ts-ingress-essdne
title: 'Ingress error: ESSDNE'
description: Troubleshoot Ingress ESSDNE (Exposed Service Set Does Not Exist) errors.
last-updated: 2026-08-12
---

> ## 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.

# Ingress error: ESSDNE
{: #ts-ingress-essdne}
{: troubleshoot}
{: support}

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

Troubleshoot Ingress ESSDNE (Exposed Service Set Does Not Exist) errors.
{: shortdesc}


When you check the status of your cluster's Ingress components by running the **`ibmcloud oc ingress status-report get`** command, you see an error similar to the following example.
{: tsSymptoms}

```sh
The secret is not present on the cluster or is in the wrong namespace (ESSDNE).
```
{: screen}

A secret created via the **`ibmcloud oc ingress secret create`** command was manually deleted from the cluster.
{: tsCauses}

If the secret is no longer needed, delete it. If the secret is still needed, reapply it to the cluster.
{: tsResolve}


- If the secret is no longer needed, run the **`ibmcloud oc ingress secret rm`** command to remove it from the managed secret list.
- If the secret is still needed, run the **`ibmcloud oc ingress secret update`** command to reapply the secret to the cluster.


If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/support?topic=support-using-avatar&format=markdown). In the case details, be sure to include any relevant log files, error messages, or command outputs.