Open
Description
Bug Description
For a service behind elasti that redirects with 302
status code, the pod does come up when called, but returns a 500
Steps to Reproduce
- Normal elasti installation
- Service returning 302 for redirection
- Call the service endpoint, get 500 instead of 302
Expected Behavior
302 should be returned
Actual Behavior
500 is returned
Environment
- Kubernetes version: 1.33
- Elasti version: 0.1.14
- Installation method (helm/manual): helm
- values.yaml used: default
- External components in the request path (ingress, service mesh, etc.): istio
- Autoscaler used (HPA/Keda): keda
- Cloud provider (if applicable): aws