Classic clusters: Why can't my app connect via Ingress?

Classic infrastructure

You exposed your app by creating an Ingress resource for your app in your classic cluster.

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

First, check that your cluster is fully deployed and has at least 2 worker nodes available per zone to ensure high availability for your ALB.

ibmcloud ks worker ls --cluster <cluster_name_or_ID>

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?.
• For other issues, troubleshoot your Ingress setup by following the steps in Debugging Ingress.