Why does the Ingress status show an ERRADNF error?

Virtual Private Cloud Classic infrastructure

You can use the ibmcloud ks ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud ks ingress status-report get command, but are ignored when calculating the overall Ingress Status.

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The ALB deployment is not found on the cluster (ERRADNF).

One or more ALBs does not have a corresponding deployment on the cluster.

Each ALB that is in enabled state must have a corresponding deployment on the cluster. Disable and re-enable each ALB that does not have a deployment.

1. Ensure that your cluster masters and worker nodes are healthy.

   • Reviewing master health.
   • Worker node states.

2. List your ALBs with the ibmcloud ks ingress alb ls command. Each ALB that is enabled must have a corresponding Deployment on the cluster.

3. List the deployments in the kube-system namespace.

   kubectl get deployments -n kube-system
   

4. Disable ALBs that don't have a deployment by using the ibmcloud ks ingress alb disable command.

5. Wait 10 minutes.

6. Re-enable ALBs by using the ibmcloud ks ingress alb enable command.

7. Wait 15-20 minutes, then check if the deployments are created.

   kubectl get deployments -n kube-system
   

8. If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.