Track: KEDA HTTP add-on evaluation for scale-to-zero HTTP services

[hortison]

Evaluating KEDA HTTP add-on for scaling HTTP services to zero in non-production environments.

Use case: Dev environment services that are idle overnight should scale to zero. KEDA HTTP add-on intercepts requests and scales up before forwarding.

Questions to answer:

• What is the cold start latency? (first request after scale-to-zero)
• Does it work with WebSockets or only HTTP?
• How does it interact with our ArgoCD Rollouts canary setup?
• Load tested with realistic traffic patterns?

Opening to track the evaluation. Will post results when done.

[yi-nuo426]

Cold start latency is the key concern. In my testing with a Node.js service: ~2-3s from zero to first response. That's acceptable for dev but not for prod. Make sure the evaluation covers this clearly so teams set expectations.

[hortison]

WebSocket support is limited in the current HTTP add-on - it proxies HTTP but WebSocket upgrades don't work cleanly. Noting this as a known limitation.