Can't Access a Kyma Endpoint (503 status code)

Symptom

You try to access a Kyma endpoint and receive the 503 status code.

Cause

This behavior might be caused by a configuration error in Istio Ingress Gateway. As a result, the endpoint you call is not exposed.

Solution

To fix this problem, restart the Pods of Istio Ingress Gateway.

1. List all available endpoints:

   kubectl get virtualservice --all-namespaces

2. To trigger the recreation of their configuration, delete the Pods of Istio Ingress Gateway:

   kubectl delete pod -l app=istio-ingressgateway -n istio-system

If the restart doesn't help, follow these steps: