-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating an ingress object with no http rules makes the controller crash loop #428
Labels
area/controller
Issues dealing with the controller
bug
Something isn't working
needs-triage
Issues that need triage
Comments
alex-bezek
added
bug
Something isn't working
area/controller
Issues dealing with the controller
needs-triage
Issues that need triage
labels
Sep 11, 2024
Looks like its probably ngrok-operator/internal/store/store.go Line 424 in 1e2367d
|
If you configure an ingress by accident with no apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: chess-bot-ngrok
namespace: chess-bot
spec:
ingressClassName: ngrok
rules:
- http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: chess-bot
port:
number: 8080
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/controller
Issues dealing with the controller
bug
Something isn't working
needs-triage
Issues that need triage
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: