txn2/kubefwd

Fixes critical issues with the Kubernetes discovery MCP tools introduced in v1.25.5. The tools were defined but their HTTP API routes were not registered, causing 404 errors.

Fixed: Missing API Routes

The following MCP tools now work correctly:

| Tool | Issue | Fix |
|------|-------|-----|
| get_pod_logs | 404 - route not registered | Added /v1/kubernetes/pods/:namespace/:podName/logs |
| list_pods | 404 - route not registered | Added /v1/kubernetes/pods/:namespace |
| get_pod | 404 - route not registered | Added /v1/kubernetes/pods/:namespace/:podName |
| get_events | 404 - route not registered | Added /v1/kubernetes/events/:namespace |
| get_endpoints | 404 - route not registered | Added /v1/kubernetes/endpoints/:namespace/:serviceName |

Fixed: Response Format Errors

| Tool | Issue | Fix |
|------|-------|-----|
| list_pods | JSON unmarshal error | Return array directly, not wrapped in object |
| get_events | JSON unmarshal error | Return array directly, not wrapped in object |

Fixed: get_connection_info Without Namespace

Previously, calling get_connection_info with only a service name (no namespace) would return 404. Now it:

1. Searches for services matching the name
2. If exactly one match, returns that service's connection info
3. If multiple matches, returns an error listing namespaces to disambiguate

# Now works:
get_connection_info(service_name="postgres")

# If ambiguous, helpful error:
"multiple services found with name 'postgres' in namespaces: [staging, production]. Please specify namespace"

Changes

• Fix missing HTTP routes for 5 MCP Kubernetes discovery tools
• Fix response format for list_pods and get_events
• Fix get_connection_info to work without namespace parameter

Full Changelog

https://github.com/txn2/kubefwd/compare/v1.25.5...v1.25.6

Changelog

• 516bdc36d71a30e47c5ff3b19c6ef5df2536829c Fix Missing Kubernetes API Routes for MCP (#351)
• 60238c7aa53f0063ef16bffb791bbd594c5c643f deps: bump github.com/bep/debounce from 1.2.0 to 1.2.1 (#344)