-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Unable to bind tcp ports #3732
Comments
@johan-smits please check if you have IPV6 enabled |
@johan-smits also, please use |
@aledbf I can confirm that the IPv6 is off. |
@johan-smits master + #3747 and #3748 Edit: In particular, https://github.com/kubernetes/ingress-nginx/pull/3748/files#diff-631c440a9ca70cdc7428a187a6820011R45 is the change fixes this issue. |
This makes sense, just needs to wait for the |
Closing. Fixed in master #3748 |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.):
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
NGINX Ingress controller version: 0.21.0
Kubernetes version (use
kubectl version
): 1.11.5Environment:
What happened:
Unable to bind tcp ports:
What you expected to happen:
It does work with version 0.17.1
How to reproduce it (as minimally and precisely as possible):
Configure a tcp map to bind the port
Anything else we need to know:
Possible broken due to this PR: #3038 and might be related to: #3668
The text was updated successfully, but these errors were encountered: