External MCP requests redirect to unreachable internal K8s URL

[RanWurmbrand]

Summary

External clients receive redirects to internal Kubernetes URLs that cannot be resolved outside the cluster.

What I Observed

When connecting to the MCP API from outside the cluster:

• Request URL: https://tackle-konveyor-tackle.apps.mig08.rhos-psi.cnv-qe.rhood.us/hub/services/kai/api/
• Server redirects to: http://tackle-hub.konveyor-tackle.svc:8080/api

This causes the following error:
Error: getaddrinfo ENOTFOUND tackle-hub.konveyor-tackle.svc

Workaround

We added client-side logic to intercept these redirects and rewrite them to use the external URL.

How to Reproduce

1. Obtain an authentication token from the Keycloak endpoint
2. Make an authenticated request to the MCP API endpoint:
   https://tackle-konveyor-tackle.apps.mig08.rhos-psi.cnv-qe.rhood.us/hub/services/kai/api/
3. Observe the redirect response pointing to tackle-hub.konveyor-tackle.svc