Console deployment fails on k3s/Kubernetes

[nbmaiti]

Problem

The Console application fails to deploy or run correctly on k3s/Kubernetes clusters using the Helm chart.

Symptoms

• Pods fail to start or crash repeatedly
• Health checks fail (readinessProbe/livenessProbe issues)
• Service-to-service communication broken (console ↔ rps, rps ↔ mpsrouter)
• Environment variables not properly injected or missing required secrets
• Web UI unreachable or routing to wrong backend URLs

Testing Required

• Deploy chart to k3d cluster with default values
• Verify console pod starts and readiness probe passes
• Confirm RPS and mpsrouter pods connect to console successfully
• Test web UI accessibility and API endpoint routing
• Validate in multi-namespace setup (not just default)
• Test with both explicit gateway.publicUrl and fallback to console.commonName