Why does the Ingress status show an ERRAHSNF 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 health service is not found on the cluster (ERRAHSNF).

IBM Cloud Kubernetes Service deploys a managed health check service to every cluster. If the service is missing from your cluster, this might result in invalid health check results.

Manually create the health service.

1. Copy the following service configuration and save it to a file called service.yaml.

   apiVersion: v1
   kind: Service
   metadata:
     name: ibm-k8s-controller-health
     namespace: kube-system
   spec:
     ports:
     - name: http
       port: 80
       protocol: TCP
       targetPort: 8283
     selector:
       alb-image-type: community
     type: ClusterIP
   

2. Create the health check service in your cluster.

   kubectl apply -f service.yaml
   

3. Wait 10-15 minutes, then retry the ibmcloud ks ingress status-report get command to see if the issue is resolved.

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