Debugging Errors from Ingress Gateway

The possible errors that you may encounter from Ingress Gateway are:
  • Check for 500 Error: If the request fails with 500 status code without Problem Details information, it means that the flow ended in ocudr-ingressgateway pod without route. You can confirm the same in the errors/exception section of the ocudr-ingressgateway pod logs. You also need to check the values.yaml file for the essential route configuration as shown below:

    Figure 5-10 Snapshot of Values.yaml file

    img/debugging-errors-ingress-gateway-values-yaml.png
  • Check for 503 Error: If the request fails with 503 status code with "SERVICE_UNAVAILABLE" in Problem Details, then it means that the nudr-drservice pod is not reachable due to some reason.

    Figure 5-11 503 Error Code

    img/troubleshoot-ingress-503-not-available.png
    You can confirm the same in the errors/exception logs of the ocudr-ingressgateway pod. Check for ocudr-nudr-drservice pod status and fix the issue.