GKE ingress controller will failed with "unhealthy" backend because of the Readiness Probe Path

[ypan887]

The xray-server template has a readiness probe to path "/"

       readinessProbe:
          httpGet:
            path: /
            port: {{ .Values.server.internalPort }}
          initialDelaySeconds: 60
          periodSeconds: 10
          failureThreshold: 10
        livenessProbe:
          httpGet:
            path: /
            port: {{ .Values.server.internalPort }}
          initialDelaySeconds: 90
          periodSeconds: 10

When installing xray on gke using it's ingress controller, health check will be created pointing to the root path and fall back to the readinessProbe path, which is still the root path.

These will result in an "unhealthy" backend service since if you ping xray from the worker node, you will see that it returns 301 at root path and thought it as unhealty. In stead, the health check should be really looking at path "api/v1/system/ping"

$ curl http://localhost:31469/api/v1/system/ping
{"status":"pong"}

$ curl http://localhost:31469/
<a href="/web">Moved Permanently</a>.

If we manually changed the health check endpoint to '"api/v1/system/ping", the backend healthy check will pass, and xray server can be reached.

You may want to update the readiness probe in the template