Knative on Kubernetes on AWS docs: istio installation istio-statsd-prom-bridge crashing

[arun-gupta]

Expected Behavior

Following https://github.com/knative/docs/blob/master/install/Knative-with-any-k8s.md to setup knative on a k8s cluster on AWS created using kops.

kubectl get pods -n istio-system

should give a running or completed set of pods

Actual Behavior

Instead, pod istio-statsd-prom-bridge is in CrashLoopBackOff state.

$ kubectl get pods -n istio-system
NAME                                       READY     STATUS             RESTARTS   AGE
istio-citadel-7bdc7775c7-dcvvd             1/1       Running            0          3m
istio-cleanup-old-ca-hzcgc                 0/1       Completed          0          3m
istio-egressgateway-795fc9b47-fvfrs        1/1       Running            0          3m
istio-ingress-84659cf44c-4cjxz             1/1       Running            0          3m
istio-ingressgateway-7d89dbf85f-8bs7n      1/1       Running            0          3m
istio-mixer-post-install-9cvjw             0/1       Completed          0          3m
istio-pilot-66f4dd866c-f8g2s               2/2       Running            0          3m
istio-policy-76c8896799-q7mks              2/2       Running            0          3m
istio-sidecar-injector-645c89bc64-g25b4    1/1       Running            0          3m
istio-statsd-prom-bridge-949999c4c-zqjdn   0/1       CrashLoopBackOff   5          3m
istio-telemetry-6554768879-r4w42           2/2       Running            0          3m

Steps to Reproduce the Problem

https://gist.github.com/arun-gupta/9603b93a0bb4fb6c4817d078d14cf5fd

Additional Info

This seems quite similar to #358 and likely related to knative/serving#1954 and knative/serving#1921

Tried installing Istio 0.8.0 from https://github.com/istio/istio/releases/tag/0.8.0 and got the same result.

[samodell]

Closing this as a duplicate to #358, since the discussion seems to be taking place there.

[dvins]

@samodell Please consider reopening, this issue pertains to Amazon AWS, #358 pertains to Microsoft Azure fabric.

[dvins]

@samodell Thank you.

[samodell]

The related serving issues are marked as fix, so I'm guessing this issue has been resolved.