I installed istio v1.1.1
using the available helm chart.
I have
$ kubectl get svc istio-ingressgateway -n istio-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
istio-ingressgateway LoadBalancer 10.31.251.20 35.189.53.230 80:31380/TCP,443:31390/TCP,31400:31400/TCP,15029:31920/TCP,15030:32305/TCP,15031:31084/TCP,15032:31163/TCP,15443:32714/TCP,15020:30964/TCP 3h
Then, I created a gateway and virtual service as follows:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: myservice-gateway
namespace: stg
spec:
selector:
istio: ingressgateway # use Istio default gateway implementation
servers:
- hosts:
- "stg.myservice.com"
port:
number: 80
protocol: http
name: http-myservice-port
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: myservice
namespace: stg
spec:
hosts:
- "stg.myservice.com"
gateways:
- myservice-gateway
http:
- match:
- uri:
prefix: /
route:
- destination:
port:
number: 8888
host: myservice-service.stg.svc.cluster.local
I have made sure that the service is running correctly and when I port forward the pod, I can access it using localhost.
I can confirm that stg.myservice.com
resolves to 35.189.53.230
.
I get this error
$ curl -i stg.myservice.com
HTTP/1.1 404 Not Found
location: http://stg.myservice.com/
date: Sun, 07 Apr 2019 05:54:59 GMT
server: istio-envoy
content-length: 0
What am I missing?
I see no errors in the ingress-gateway
pod
PS: I have gateways.istio-ingressgateway.sds.enabled=true
In your virtualservice config you'll want to add a namespace to the gateway
stg/myservice-gateway
instead of
myservice-gateway
so something like this
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: myservice
namespace: stg
spec:
hosts:
- "stg.myservice.com"
gateways:
- stg/myservice-gateway
http:
- match:
- uri:
prefix: /
route:
- destination:
port:
number: 8888
host: myservice-service.stg.svc.cluster.local
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With