Skip to content

docs(kagent): Add WSL2 port-forward fix to README #177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
24f3005089 wants to merge 1 commit into
base: main
Choose a base branch
from
+14 −1
Open

docs(kagent): Add WSL2 port-forward fix to README #177

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion kagent-feast-mcp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,9 @@ kubectl get agents,remotemcpservers,modelconfigs -n <YOUR_NAMESPACE>
### Step 7: Access kagent UI

```bash
kubectl -n <YOUR_NAMESPACE> port-forward service/kagent-ui 8080:8080
# WSL2 users: Add --address=0.0.0.0 to avoid connection drops
kubectl -n <YOUR_NAMESPACE> 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.
Expand All @@ -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 <YOUR_NAMESPACE> port-forward --address=0.0.0.0 service/kagent-ui 8080:8080



### Debug Commands

```bash
Expand Down