From 78cf8c023a4d7e7a97b36d304c1438f14ad7fcac Mon Sep 17 00:00:00 2001 From: navidgh67 Date: Thu, 15 Oct 2026 22:01:21 -0400 Subject: [PATCH] Route /api/assistant to dt-web in the ingress The ingress only sends /api/auth, /api/mcp, /api/dt and /api/tools to dt-web. All other /api paths go to FastAPI, so the assistant's chat endpoint (POST /api/assistant) got a 404 from dt-api in production. This adds /api/assistant to dt-web, next to the other Next.js API prefixes. Co-Authored-By: Claude Opus 5.5 --- geddes/k8s/04-ingress.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/geddes/k8s/04-ingress.yaml b/geddes/k8s/04-ingress.yaml index 70bab7f..896235f 100644 --- a/geddes/k8s/04-ingress.yaml +++ b/geddes/k8s/04-ingress.yaml @@ -51,6 +51,15 @@ spec: port: number: 3000 + # 3c. /api/assistant goes to the Next.js AI assistant route + - path: /api/assistant + pathType: Prefix + backend: + service: + name: dt-web + port: + number: 3000 + # 4. Next longest match: /api goes to FastAPI # FastAPI is natively configured to handle /api routes so no rewrite is needed! - path: /api