Port 9090 declared in manifests but no metrics server listening

[yairfalse]

Summary

The DaemonSet manifest and kind config both declare port 9090 for Prometheus metrics, but RAUTA doesn't bind a listener on that port. Only ports 80 (proxy) and 9091 (admin) are active.

Steps to reproduce

# Deploy RAUTA to kind
./deploy/deploy-to-kind.sh

# Try to scrape metrics
curl http://localhost:9090/metrics
# Connection refused

# Verify from inside the pod
kubectl exec -n rauta-system <pod> -- cat /proc/net/tcp
# Only 0x0050 (80) and 0x2383 (9091) are listening

Expected

Prometheus exposition format metrics available at http://<node>:9090/metrics, including:

• http_requests_total (counter by method, path, status)
• http_request_duration_seconds (histogram)

Actual

Nothing listens on port 9090. Operational data is only available through the admin REST API on :9091 (/api/v1/status, /api/v1/cache, /api/v1/routes).

Impact

• Prometheus/Grafana can't scrape RAUTA
• The rauta-metrics ClusterIP Service (port 9090) has no target
• Grafana dashboards in deploy/grafana/ won't work without a metrics endpoint

Affected manifests

• deploy/rauta-daemonset.yaml — declares containerPort 9090
• deploy/kind-config.yaml — maps containerPort 9090 → hostPort 9090
• deploy/rauta-daemonset.yaml — rauta-metrics Service targets port 9090

Discovered during

Luotain blackbox testing — sent 150 requests through the proxy, then attempted to verify Prometheus metrics.