-
Notifications
You must be signed in to change notification settings - Fork 269
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
Crashes with ExternalName service #336
Comments
This makes it not crash (but doesn't make the ExternalService work).
|
This seems to work with the 0.10 beta now. :-) |
Hi, I definitely missed this issue; need to make a triage on all of the opened ones. Sorry about taking so long. This was fixed on #455 and should work fine on the latest tag of all branches - currently v0.8.4, v0.9, and also v0.10-beta.1 as you pointed out. Thanks for the report and feedback. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In an older cluster I had a service with an externalName service. Moving to a new cluster with a newer haproxy-ingress, the ingress crashes with this.
The text was updated successfully, but these errors were encountered: