Why does the Ingress status show an `ERRHPAIWC` error?

Virtual Private Cloud Classic infrastructure Satellite

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 cluster does not have enough worker nodes to satisfy the autoscaling configuration (ERRHPAIWC).

The cluster does not have enough compatible workers to meet the replica count specified in your ALB autoscaler configuration.

Determine the number of required worker nodes. Then, update your autoscaler configuration replica count or add extra workers to your cluster to accommodate the requirements.

For more information on ALB autoscaling, see Dynamically scaling ALBs with autoscaler.

List your ALBs. In the output, identify the ALB that is relevant to the autoscaler error. For classic clusters, note the ALB type and VLAN. For VPC clusters, note the ALB zones.
```
ibmcloud ks ingress alb ls -c <clusterID>
```
List and count the total number of worker nodes that are compatible with ALBs. If your cluster has dedicated edge nodes, then ALBs are scheduled only to those nodes. In this case, include the --selector dedicated=edge option in the above commands.

If your cluster has dedicated edge nodes, then ALBs are scheduled only to those nodes. In this case, include the --selector dedicated=edge option in the above commands.
- Classic cluster with public ALB
```
kubectl get nodes --selector publicVLAN=<ALB VLAN>
```
- Classic cluster with private ALB
```
kubectl get nodes --selector privateVLAN=<ALB VLAN>
```
- VPC cluster
```
kubectl get nodes --selector ibm-cloud.kubernetes.io/zone=<ALB zone>
```
Update the autoscaler configuration or add extra worker nodes to you cluster to accommodate the number of nodes found in the previous step.
- To update the autoscaler configuration
  1. Get the ALB autoscaler configuration.
```
ibmcloud ks ingress alb autoscale get -c <clusterID> --alb <albID>
```
  2. Adjust the maximum replica count. The specified value should be equal to or less than the number of nodes found in the previous step.
  3. Apply the updated autoscaler configuration.
```
ibmcloud ks ingress alb autoscale set -c <clusterID> --alb <albID>
```
- To add extra worker nodes to the cluster
  1. Follow the steps in Adding worker nodes to Classic clusters or Adding worker nodes to VPC clusters. Make sure to add workers to the appropriate zone and VLAN identified in previous steps. If you are using edge nodes, label them as dedicated=edge.
Wait 15 to 20 minutes for the changes to apply. Then check if the warning is resolved.
If the issue persists, contact support. Include a detailed list of the troubleshooting steps you took. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.

Why does the Ingress status show an ERRHPAIWC error?

Why does the Ingress status show an `ERRHPAIWC` error?