vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why does the Ingress status show an ERRDSAISS error? 

Virtual Private Cloud

Classic infrastructure

Satellite

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.

  What’s happening 

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 external provider for the given subdomain has authorization issues (ERRDSAISS).

  Why it’s happening 

The Kubernetes Service is unable to access the external domain provider used for the given subdomain.

  How to fix it 

Complete the following steps based on your external domain provider.



*  For external Akamai or Cloudflare domains, make sure that you create a valid credential for the cluster by using ibmcloud ks ingress domain credential set command.
*  For domains provisioned with Cloud Internet Services, ensure that the service-to-service authorization is in place. For more information, see [Setting up domains with IBM Cloud Internet Services](https://cloud.ibm.com/docs/containers?topic=containers-ingress-domainsingress-domain-cis). If you no longer want to use the domain you registered, then you can remove it by using the ibmcloud ks ingress domain rm --c CLUSTER --domain DOMAIN command.
Warning SyncLoadBalancerFailed 55s service-controller Error syncing load balancer: failed to ensure load balancer: Error on cloud load balancer kube-<CLUSTERID>-<SERVICE_UUID> for service <NAMESPACE>/<SERVICE_NAME> with UID <SERVICE_UUID>:: Failed ensuring LoadBalancer: FindLoadBalancer failed: FindLoadBalancer failed: An error occurred while performing the 'authenticate' step: 400 Bad Request [{"incidentID":"XXX","code":"XXX","description":"Error message from IAM: '401 Unauthorized. Transaction-Id: XXX Details: {"errorCode":"BXNIM0430E","errorMessage":"User login from given IP address is not permitted.","errorDetails":"The user has configured IP address restriction for login. The given IP address 'XXX' is not contained in the list of allowed IP addresses.","context":...,"type":"Authentication"}]

 Why it’s happening 

This error occurs when your IAM allowlist doesn't allow the necessary communication to control plane IPs.

 How to fix it 

To resolve this issue, add the control plane IPs for the region where your cluster is located to your IAM allowlist.

For a list of control plane IPs by region, see the IBM/kube-samples[repo](https://github.com/IBM-Cloud/kube-samples/tree/master/control-plane-ips)
* BEARER_SUB_EXTRACTION_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-bearer-sub-extraction-err)
* BODY_QUERY_PARAM_MISMATCH_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-body-query-param-mismatch-err)
* COLLECTION_TOTAL_MISMATCH_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-collection-total-mismatch-err)
* CONFIG_RULE_CONFLICT_ERR [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-config_rule_conflict_err)
* FEATURE_RESTRICTED_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-feature-restricted-err)
* IMPORT_TOKEN_EXPIRED_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-import-token-expired-err)
* INCOMPLETE_METADATA_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-incomplete-metadata-err)
* INCORRECT_NONCE_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-incorrect-nonce-err)
* INCORRECT_NONCE_IV_ERR - [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-incorrect-nonce-iv-err)