Skip to content

[BUG] Elasti does not handle redirection properly #145

Open
@shubhamrai1993

Description

@shubhamrai1993

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

  1. Normal elasti installation
  2. Service returning 302 for redirection
  3. 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

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions