Quick Sanity Check on Plain Istio Setup

1

Hi there! I am new to Istio, have had lots of success running it in a clean EKS cluster in AWS. Now I’m moving onto getting it working in a crufty old cluster in AWS which was created via Kops and which has some tweaked networking/VPC things going on.

If someone has five minutes to vet this config, I am having trouble with simply getting traffic in over port 8080. My Istio 1.5-prelim was installed via helm template, demo profile. I hand-edited the Istio Ing GW so that it listens to port 8080, not 80. I think I have a port numbering issue somewhere in this Yaml:

---
apiVersion: v1
kind: Service
metadata:
  name: httpbin
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*"
    service.beta.kubernetes.io/aws-load-balancer-backend-protocol: http
spec:
  type: LoadBalancer
  ports:
  - port: 8080
    name: http
    targetPort: 80
  selector:
    app: httpbin

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: httpbin
spec:
  selector:
    matchLabels:
      app: httpbin
  template:
    metadata:
      labels:
        app: httpbin
    spec:
      containers:
      - image: docker.io/kennethreitz/httpbin
        name: httpbin
        ports:
        - containerPort: 80
          name: http

---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: httpbin-gw
spec:
  selector:
    istio: ingressgateway
  servers:
  - port:
      number: 8080
      name: http
      protocol: HTTP
    hosts:
    - "*"

---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: httpbin-vs
spec:
  hosts:
  - "*"
  gateways:
  - httpbin-gw
  http:
  - match:
    - uri:
        prefix: /
    route:
    - destination:
        host: httpbin
      weight: 100