From 5c7f5389f2c9a83fc5db448675bb84ff356282ed Mon Sep 17 00:00:00 2001 From: 24f3005089 <24f3005089@ds.study.iitm.ac.in> Date: Fri, 27 Mar 2026 12:20:04 +0530 Subject: [PATCH] docs(kagent): Add WSL2 port-forward fix to README Signed-off-by: 24f3005089 <24f3005089@ds.study.iitm.ac.in> --- kagent-feast-mcp/README.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/kagent-feast-mcp/README.md b/kagent-feast-mcp/README.md index be9cec7..5723237 100644 --- a/kagent-feast-mcp/README.md +++ b/kagent-feast-mcp/README.md @@ -167,7 +167,9 @@ kubectl get agents,remotemcpservers,modelconfigs -n ### Step 7: Access kagent UI ```bash -kubectl -n port-forward service/kagent-ui 8080:8080 +# WSL2 users: Add --address=0.0.0.0 to avoid connection drops +kubectl -n port-forward --address=0.0.0.0 service/kagent-ui 8080:8080 + ``` Open http://localhost:8080 in your browser to interact with the Kubeflow docs agent. @@ -186,6 +188,17 @@ kill %1 - **Port-forward works, direct fails** -- Istio blocking. Run `kubectl apply -f ../manifests/istio/` +### WSL2 port-forward connection drops + +If you're running on WSL2 and the Kagent UI loads but becomes unresponsive or shows 504 Gateway errors, the default kubectl port-forward command may not work reliably due to WSL2's NAT bridging limitations. + +Solution: Add --address=0.0.0.0 to bind to all interfaces: + +```bash +kubectl -n port-forward --address=0.0.0.0 service/kagent-ui 8080:8080 + + + ### Debug Commands ```bash