Currently running istio off the release-1.1 branch. I used helm to install and had it create the default ingressgateway as well as the ilbgateway and modified the annotation for AWS internal instead of google. I can curl the internal ELB and get a 404 which I think tells me that the ingress is mostly functioning. However when i take the httpbin example and modify it to try and use the internal ingress, I still get 404s. y gateway and virtual service definition is below. I’m using external-dns to create the r53 entry and have confirmed its creating it based on the ILB fqdn, not the external one. What am I missing?
Thanks
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: httpbin-gateway
namespace: default
annotations:
kubernetes.io/ingress.class: internal
spec:
selector:
istio: ilbgateway # use Istio default gateway implementation
servers:
- port:
number: 80
name: http
protocol: HTTP
hosts:
- "httpbin.internal.domain"
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: httpbin
namespace: default
spec:
hosts:
- "httpbin.internal.domain"
gateways:
- httpbin-gateway
http:
- match:
- uri:
prefix: /ip
route:
- destination:
port:
number: 8000
host: httpbin.default.svc.cluster.local