-
Notifications
You must be signed in to change notification settings - Fork 2k
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
IPv6 SVCs not supported (missing [ ]
)
#991
Comments
Hi @Frankkkkk We don't support IPv6 in the Ingress Controller, unfortunately. I can't share any ETA. I suggest leaving this issue open. We'll use it to track this feature. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Still present :-) |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Still present :-) |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
/unstale |
Thanks @Frankkkkk. IPv6 support is something I have added to our roadmap. |
Hi @brianehlert. Is this still on the road map now that #2361 is available? |
PR 2361 is not yet available in Main, therefore it is still on the roadmap ;-) |
Fixed in #2576 |
Describe the bug on IPv6 kubernetes clusters (and thus SVCs with IPv6 addresses), the nginx configuration for the ingress is wrongly generated and thus doesn't work
To Reproduce Steps to reproduce the behavior:
Get an IPv6 only kubernetes cluster. And create an ingress pointing to a IPv6 svc. For example:
$ kl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 2001:1600:aaa:bbb:ffff::1 <none> 443/TCP 3d4h
Then create a simple ingress:
yaml apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test spec: rules: - host: foo.bar.com http: paths: - path: / backend: serviceName: kubernetes servicePort: 443
This generates a wrong nginx configuration ``` upstream default-simple-fanout-example-foo.bar.com-kubernetes-443 { --- snip --- server 2001:1600 max_fails=1 fail_timeout=10s max_conns=0;
}
**Expected behavior** The IPv6 should not be truncated and enclosed in brackets:
server [2001:1600:aaa:bbb:ffff::1] max_fails=1 fail_timeout=10s max_conns=0;```
Your environment * Version of the Ingress Controller: GitCommit=7d341058 * Version of Kubernetes: v1.17.6 * Using NGINX or NGINX Plus: NGINX
Aha! Link: https://nginx.aha.io/features/IC-104
The text was updated successfully, but these errors were encountered: