Why does the Ingress status show an ERRSNF 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.

The load balancer service is missing (ERRSNF).

ALBs are exposed using LoadBalancer services, but one or more of these services are missing from the cluster.

Disable and re-enable your Ingress ALB.

1. List your ALBs.

   ibmcloud ks ingress alb ls -c <cluster>
   

2. List the services in the kube-system namespace.

   kubectl get services -n kube-system
   

3. Review the ALB and services lists to look for missing services.

   Classic

   All ALBs that have an enabled state must have an existing LoadBalancer service with a name matching the ALB IDs.

   VPC

   If you have at least one public ALB in enabled state, there must be an existing public LoadBalancer service having the public-cr-CLUSTER-ID prefix in its name. Similarly, if you have at least one private ALB in enabled state, there must be an existing private LoadBalancer service having the private-cr-CLUSTER-ID prefix in its name.

4. Complete the following steps for each missing service.

   1. Disable the corresponding ALB using the ibmcloud ks ingress alb disable command.
   2. Wait until the ALB deployment is removed from the kube-system namespace.
   3. Re-enable the ALB using the ibmcloud ks ingress alb enable command.
   4. Wait 10 to 15 minutes, then check that the LoadBalancer services are created.

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