From c13fd8ce807c6ca3916b5f5a2f60842e28f3e9d4 Mon Sep 17 00:00:00 2001 From: Jeremy Eder Date: Wed, 12 Nov 2025 16:41:45 -0500 Subject: [PATCH] fix: remove backend-ingress to resolve auth token routing conflict MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The backend-ingress was intercepting /api/* requests before they could reach the Next.js frontend, causing authentication failures. The frontend serves both the UI and API routes, proxying authenticated requests to the backend internally via backend-service:8080/api. This eliminates the "Invalid or missing token" error users saw when accessing the UI after running setup-kind.sh and deploy.sh. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- components/manifests/overlays/e2e/kustomization.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/manifests/overlays/e2e/kustomization.yaml b/components/manifests/overlays/e2e/kustomization.yaml index 1c46688d1..32b5dc6e8 100644 --- a/components/manifests/overlays/e2e/kustomization.yaml +++ b/components/manifests/overlays/e2e/kustomization.yaml @@ -9,7 +9,7 @@ resources: - secrets.yaml - test-user.yaml - frontend-ingress.yaml -- backend-ingress.yaml +# backend-ingress.yaml removed - frontend handles all routing and proxies to backend internally - operator-config.yaml # Patches for e2e environment