-
Notifications
You must be signed in to change notification settings - Fork 14
Getting Started Tutorial: Debug Reaction in GitHub Codespaces setting shows 404 due to ingress host header mismatch #194
Copy link
Copy link
Open
drasi-project/learning
#82Labels
bugSomething isn't workingSomething isn't working
Description
Issue:
Following the step 4 of Getting Started guide on Drasi website, under the GitHub Codespaces setup, noticed that the browser is showing 404 page not found.
Details:
The port-forward on 8080 is pointing at the traefik ingress controller, and the ingress expects the host header hello-world-debug.drasi.127.0.0.1.nip.io. But when I access it via the Codespaces URL, the host header is congenial-fishstick-...app.github.dev, which doesn't match — so traefik returns 404.
$ kubectl get svc -n drasi-system | grep hello-world-debug
hello-world-debug-gateway ClusterIP 10.43.153.122 8080/TCP 21m
hello-world-debug-reaction-dapr ClusterIP None 80/TCP,50001/TCP,50002/TCP,9090/TCP 21m
hello-world-debug-reaction-service ClusterIP 10.43.6.235 8080/TCP 21m
$ kubectl get ingress -A
NAMESPACE NAME CLASS HOSTS ADDRESS PORTS AGE
drasi-system hello-world-debug-reaction-ingress traefik hello-world-debug.drasi.127.0.0.1.nip.io 172.18.0.2 80 21m
$ ps aux | grep port-forward
vscode 12252 0.0 0.3 5478532 51440 ? Sl 14:38 0:00 kubectl port-forward svc/postgres 5432:5432
vscode 12271 0.0 0.3 5478532 52316 ? Sl 14:38 0:00 kubectl port-forward -n kube-system svc/traefik 8080:80Workaround:
Kill the traefik port-forward and port-forward directly to the gateway service:
kubectl port-forward svc/hello-world-debug-gateway 8080:8080 -n drasi-system
Suggested fix:
Update the setup script to port-forward to the gateway service instead of traefik, or document this (at _index.md) as a known issue.
Happy to submit a PR to fix this :)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working