---
name: containers-ts-ingress-must-gather
title: Gathering Ingress details for debugging
description: Run the following commands to gather the required logs and details for debugging Ingress.
last-updated: 2026-04-30
---

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

# Gathering Ingress details for debugging
{: #ingress-must-gather}
{: support}

Run the following commands to gather the required logs and details for debugging Ingress.
{: shortdesc}

1. Get nodes and node labels.

    ```sh
    kubectl get nodes --show-labels
    ```
    {: pre}
    
1. Get endpoints.

    ```sh
    kubectl get endpoints -o wide
    ```
    {: pre}

1. Get the Ingress status.

    ```sh
    ibmcloud ks ingress status-report get -c CLUSTERID
    ```
    {: pre}
    



1. List ALBs.

    ```sh
    ibmcloud ks ingress alb ls -c CLUSTERID
    ```
    {: pre}

1. Describe your Ingress resource.

    ```sh
    kubectl describe ing <ingress name> -n <namespace>
    ```
    {: pre}
    
1. Get the logs for the `nginx-ingress` container in your Ingress pods.

    ```sh
    kubectl logs <ingress pods> -n kube-system -c nginx-ingress
    ```
    {: pre}
    
1.  List host names for network load balancer (NLB).

    ```sh
    ibmcloud ks nlb-dns ls -c CLUSTERID
    ```
    {: pre}

1. List the `alb` pods in the `kube-system` namespace.

    ```sh
    kubectl get pods -n kube-system | grep alb
    ```
    {: pre}



1. List your cluster subdomains.
    ```sh
    ibmcloud ks ingress domain ls -c CLUSTERID
    ```
    {: pre}
    
1. Run an `nslookup` on your Ingress subdomain.

    ```sh
    nslookup ingresssubdomain.com
    ```
    {: pre}
    

1. Save the information you've gathered and 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.