---
name: containers-ts-ingress-app
title: 'Classic clusters: Why can''t my app connect via Ingress?'
description: '[Classic infrastructure]'
last-updated: 2026-07-27
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?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.

# Classic clusters: Why can't my app connect via Ingress?
{: #cs_ingress_fails}
{: support}

[Classic infrastructure]{: tag-classic-inf}



You exposed your app by creating an Ingress resource for your app in your classic cluster.
{: tsSymptoms}

When you tried to connect to your app by using the public IP address or Ingress subdomain, the connection failed or timed out.
{: tsCauses}


Check that your cluster is fully deployed and has at least 2 worker nodes available per zone to ensure high availability for your ALB.
{: tsResolve}

```sh
ibmcloud ks worker ls --cluster CLUSTER_NAME_OR_ID
```
{: pre}

In your CLI output, make sure that the **Status** of your worker nodes displays **Ready** and that the **Machine Type** shows a flavor other than **free**.

- If your standard cluster is fully deployed and has at least 2 worker nodes per zone, but no **Ingress Subdomain** is available, see [Why does no Ingress subdomain exist after cluster creation?](https://cloud.ibm.com/docs/containers?topic=containers-ingress_subdomain&format=markdown).
- For other issues, troubleshoot your Ingress setup by following the steps in [Debugging Ingress](https://cloud.ibm.com/docs/containers?topic=containers-ingress-debug&format=markdown).