/istio/istio/tree/release-0.7/samples/helloworld ingress broke (all ingress really)

[mabushey]

Is this a BUG or FEATURE REQUEST?:

Did you review https://istio.io/help/ and existing issues to identify if this is already solved or being worked on?: yes

Bug:
Y

What Version of Istio and Kubernetes are you using, where did you get Istio from, Installation details

ubuntu@bast ~/kops/istio/samples/helloworld$ kubectl get svc istio-ingress                                                                                           ✹ ✭release-0.7 
Error from server (NotFound): services "istio-ingress" not found
ubuntu@bast ~/kops/istio/samples/helloworld$ istioctl version                                                                                                   1 ↵  ✹ ✭release-0.7 
Version: 0.7.1
GitRevision: 62110d4f0373a7613e57b8a4d559ded9cb6a1cc8
User: root@c5207293dc14
Hub: docker.io/istio
GolangVersion: go1.9
BuildStatus: Clean

ubuntu@bast ~/kops/istio/samples/helloworld$ kubectl version                                                                                                         ✹ ✭release-0.8 
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1", GitCommit:"d4ab47518836c750f9949b9e0d387f20fb92260b", GitTreeState:"clean", BuildDate:"2018-04-12T14:26:04Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T11:55:20Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}

Installed Istio via ansible

Is Istio Auth enabled or not ?
Did you install the stable istio.yaml, istio-auth.yaml.... or if using the Helm chart please provide full command line input.
Installed istio via Ansible, I assume it did that. Grafana, jaeger, and servicegraph come up using kube port-forward.

What happened:

$ kubectl create -f helloworld-istio.yaml                                                                                 ✹ ✭release-0.7 
service "helloworld" created
deployment.extensions "helloworld-v1" created
deployment.extensions "helloworld-v2" created
ingress.extensions "helloworld" created

Note - The instructions on adding the cpu:100m appear obsolete, they were already there.

$ grep cpu helloworld-istio.yaml                                                                                          ✹ ✭release-0.7 
            cpu: 100m
            cpu: 100m

ubuntu@bast ~/kops/istio/samples/helloworld$ export HELLOWORLD_URL=$(kubectl get po -l istio=ingress -o 'jsonpath={.items[0].status.hostIP}'):$(kubectl get svc istio-ingress -o 'jsonpath={.spec.ports[0].nodePort}')
error: error executing jsonpath "{.items[0].status.hostIP}": array index out of bounds: index 0, length 0
Error from server (NotFound): services "istio-ingress" not found
ubuntu@bast ~/kops/istio/samples/helloworld$ kubectl get svc istio-ingress                                                                                           ✹ ✭release-0.7 
Error from server (NotFound): services "istio-ingress" not found

ubuntu@bast ~/kops/istio/samples/helloworld$ kubectl get ingress -o wide                                                                                             ✹ ✭release-0.7 
NAME         HOSTS     ADDRESS                                                                   PORTS     AGE
helloworld   *         a2c7605b853e211e880d1029cf50ebd5-1253323931.us-west-1.elb.amazonaws.com   80        27s

What you expected to happen:
To get an ingress point.

How to reproduce it:

Attempt to access a container running in kubernetes/istio. As far as I can tell, the ONLY way to access a container in kubernetes/istio is via kubectl port-forward, nothing else works.

[louiscryan]

Can you retry with 0.8.

With 0.8 you will get the new Gateway resource for Ingress.

I don't think that will cause AWS to autoprovision and ingree LB for you.

@ZackButcher might have a better idea here