You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add Kubernetes manifests and Tiltfile integration for MCP server (#1209)
* feat: add Kubernetes manifests and Tiltfile integration for MCP server
Creates k8s manifests (configmap, secret, deployment, service) for the
MCP server in services/mcp-server/k8s/ and adds docker_build, k8s_yaml,
and k8s_resource entries to the Tiltfile for local development.
The MCP server runs SSE transport on port 8090, connects to the gateway
for all backend gRPC calls, and port-forwards on 18090 locally to avoid
conflict with the gateway's 8090 port-forward.
* fix: use TCP socket probes for MCP server health checks
The /sse endpoint is a long-lived SSE stream (it never sends a 200 and
returns), making it unsuitable as an httpGet probe target. Switch to
tcpSocket probes which verify the port is accepting connections without
coupling health checks to transport semantics.
* fix: correct labels and add gateway init container in mcp-server manifests
- Change component label from mcp-gateway to mcp-server across all manifests
- Change tier label from frontend to backend in deployment.yaml (MCP server
is a backend API adapter, not a frontend component)
- Add wait-for-gateway init container to ensure gateway is ready before the
MCP server starts (complements the existing wait-for-control-plane check)
* fix: add readOnlyRootFilesystem to init container security contexts
Harden init container security contexts to match the main container by
adding readOnlyRootFilesystem: true. The busybox nc command does not
require a writable root filesystem.
---------
Co-authored-by: Ben Coombs <bjcoombs@users.noreply.github.com>
0 commit comments