fix: Update Helm chart configuration for console deployment

[nbmaiti]

Fixes #664

Issues Addressed

1. Hardcoded Namespaces: Explicit namespace: default in manifests prevents flexible multi-namespace deployments
2. Outdated Environment Variables: Old CONSOLE_* prefixed variables don't match current application configuration schema
3. Service Discovery: Incorrect service references (mps → console, wrong KUMA annotation) cause routing failures
4. Health Check Mismatch: /api/v1/health endpoint doesn't exist; should use /healthz
5. Web UI Configuration: Missing SPA routing fallback; hardcoded service names prevent multi-environment deployments
6. Code Quality: Trailing whitespace in YAML files

Solutions Implemented

Issue	Solution
Hardcoded namespaces	Removed explicit namespace: default to inherit from Helm release context
Environment variables	Reorganized into logical groups: APP_*, AUTH_*, HTTP_*, DB_*, SECRETS_*
Service references	Updated mpsrouter KUMA annotation to console_{{ .Release.Namespace }}_svc_3000; fixed RPS_MPS_SERVER to point to console
Health check	Changed readinessProbe path from /api/v1/health to /healthz
Web UI routing	Added try_files $uri $uri/ /index.html; for SPA support; replaced hardcoded commonName with {{ .Values.gateway.publicUrl }}
Code quality	Removed all trailing whitespace from YAML files

Changes

• console.yaml: Updated environment variables, health check, and removed namespace
• kong.yaml: Removed hardcoded namespaces from all Ingress resources
• mpsrouter.yaml: Fixed KUMA annotation with proper namespace template
• rps.yaml: Updated MPS server endpoint reference
• webui.yaml: Enhanced nginx config for SPA routing; added gateway.publicUrl variable
• values.yaml: Added new gateway.publicUrl configuration option

Testing Checklist

• Verify pod health checks pass in test environment
• Test service-to-service communication (console ↔ rps, rps ↔ mpsrouter)
• Validate web UI routing works correctly in multi-namespace setup
• Confirm all environment variables are correctly injected and accessible
• Check KUMA service mesh annotation resolves correctly

[Copilot]

Pull request overview

Updates the Helm chart templates to make console-related deployments more environment- and namespace-friendly, aligning service discovery, health checks, and web UI configuration with the current runtime expectations.

Changes:

• Removed hardcoded namespace: default to rely on the Helm release namespace.
• Updated routing/service references (RPS → console, Kuma direct-access service name) and fixed console readiness probe path to /healthz.
• Improved web UI nginx SPA routing and introduced gateway.publicUrl for externally-reachable API base URLs.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
charts/values.yaml	Adds new gateway.publicUrl configuration knob for browser-facing host configuration.
charts/templates/webui.yaml	Adds SPA try_files fallback and switches API URL env vars to gateway.publicUrl.
charts/templates/rps.yaml	Removes hardcoded namespace and repoints RPS_MPS_SERVER to the console service.
charts/templates/mpsrouter.yaml	Removes hardcoded namespace and fixes Kuma direct-access service annotation to be namespace-aware.
charts/templates/kong.yaml	Removes hardcoded namespaces and cleans up YAML formatting/whitespace.
charts/templates/console.yaml	Removes hardcoded namespace, updates readiness probe path, and replaces legacy CONSOLE_* env vars with new grouped configuration.
chart-fixes.diff	Adds a patch artifact file mirroring the PR changes.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.