istio: 1.1-pre Legacy Ingress Resource not working correctly

pre-1.1 HEAD release-1.1-20181213-09-16 istio build does not process k8s ingress resource correctly, it assigns an incorrect IP address as shown below.

mjog@devinstance:/mnt/disks/sdb/go/src/istio.io/tools/perf/istio$ ik g ing
kubectl --namespace istio-system get ing
NAME                        HOSTS                                 ADDRESS         PORTS     AGE
cm-acme-http-solver-4vh4r   fortionoistio.v11mcp.qualistio.org                    80        3m
cm-acme-http-solver-58wtv   prom.v11mcp.qualistio.org                             80        3m
cm-acme-http-solver-fnkpj   grafana.v11mcp.qualistio.org          35.232.246.92   80        3m
cm-acme-http-solver-lpzvg   fortiotls.v11mcp.qualistio.org        35.232.246.92   80        3m
cm-acme-http-solver-mf5kz   kiali.v11mcp.qualistio.org                            80        3m
cm-acme-http-solver-vzdpj   fortionoistio1.v11mcp.qualistio.org                   80        3m
mjog@devinstance:/mnt/disks/sdb/go/src/istio.io/tools/perf/istio$ ik g svc | grep ingress                                                                                                             
istio-ingressgateway        LoadBalancer   10.19.253.28    35.224.157.11      6h

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 33 (33 by maintainers)

Most upvoted comments

@mandarjog @costinm @rshriram @louiscryan @frankbu @andraxylia do you see any value to continue support istio’s old ingress in v1.1? We already given user a grace period (which is istio v1.0) to either transition to the new istio gateway or continue using their existing ingress controller (e.g. nginx).

I don’t… I don’t think user will be using istio’s old ingress regardless. I had thought it is a simple fix, but it seems totally broken and can take lots of effort to support it.

I recommend we drop istio’s old ingress support in v1.1.

cc @wenchenglu @duderino @dcberg

linsun on Jan 24, 2019