503 Errors on Launch when Istio is configured to inject proxy sidecars

[njhale]

Describe the bug
When Istio is configured on a k8s cluster such that istio-proxy sidecars are injected into MCP server pods deployed by Obot, users can run into MCP Server Launch Failed with 503 errors at launch.

To Reproduce
Steps to reproduce the behavior:

1. In the Obot admin UI, where Obot is deployed to a k8s cluster with istio sidecar injection enabled, go to MCP Management -> MCP Servers
2. Click on a remote MCP server (e.g. Gmail, Atlassian, etc)
3. Click Connect to Server
4. Wait 10-15 seconds
5. Encounter launch error

Expected behavior
Obot waits the full 60 seconds to detect readiness before showing a non-terminal launch error.

Screenshots

Additional context

• If you don't delete the server instance, it will eventually become healthy and can be connected to with external MCP clients
• This was first observed with a remote MCP server (specifically Atlassian), but the problem may exist with single/multi user servers as well