You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to create a minimal ingress object in order to attach a traffic policy to. Since its a redirect, I don't care about the path or other rules, just the domain, so I tried to create an ingress object like this
This ingress object causes the leader pod to crash, so a new pod takes over as leader which crashes, which continues till they are all down and ingress stops working
NAME READY STATUS RESTARTS AGE
kubernetes-ingress-controller-manager-849d479c4d-2lqn8 0/1 CrashLoopBackOff 6 (2m40s ago) 10m
kubernetes-ingress-controller-manager-849d479c4d-hhxnm 0/1 CrashLoopBackOff 6 (118s ago) 10m
kubernetes-ingress-controller-manager-849d479c4d-lb5m5 0/1 CrashLoopBackOff 6 (2m22s ago) 10m
What you think should happen instead
At the very least this should not cause the controller to crash which would result in an outage for someone.
Ideally, this configuration would be accepted and result in a end with no routes assuming that would work with a traffic policy to handle redirects
How to reproduce
create an ingress object in the cluster with no rules, sit back and watch them start crashing
The text was updated successfully, but these errors were encountered:
Kubernetes Version
1.28
Helm Chart Version
0.15.0
Ingress Controller Version
0.12.0
System Info
Testing in EKS
Kubernetes Logs
Helm Chart configuration
standard
What happened
Tried to create a minimal ingress object in order to attach a traffic policy to. Since its a redirect, I don't care about the path or other rules, just the domain, so I tried to create an ingress object like this
This ingress object causes the leader pod to crash, so a new pod takes over as leader which crashes, which continues till they are all down and ingress stops working
What you think should happen instead
At the very least this should not cause the controller to crash which would result in an outage for someone.
Ideally, this configuration would be accepted and result in a end with no routes assuming that would work with a traffic policy to handle redirects
How to reproduce
create an ingress object in the cluster with no rules, sit back and watch them start crashing
The text was updated successfully, but these errors were encountered: