Custom Gateways for multiple environments/hosts

Networking
2

Hey @joznox
So, it is correct that the GW does not need to be in the same ns as the Ingress deployment.
Now, the 404 may indicate the host header is not properly set or the VirtualService attached to the GW is not matching the given path.
Notice how in the first example I’ve set header "host: httpbi.com" (I missed the last n)

  —————»  ns:httpbin-a ❯ curl http://127.0.0.1:8080/status/201 -H"host: httpbi.com" -v -s -o /dev/null                           
*   Trying 127.0.0.1:8080...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /status/201 HTTP/1.1
> Host: httpbi.com
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 404 Not Found
< date: Mon, 18 Dec 2023 07:04:01 GMT
< server: istio-envoy
< content-length: 0
< 
* Connection #0 to host 127.0.0.1 left intact
[8:04:01] ~ ()
  —————»  ns:httpbin-a ❯ curl http://127.0.0.1:8080/status/201 -H"host: httpbin.com" -v -s -o /dev/null 
*   Trying 127.0.0.1:8080...
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /status/201 HTTP/1.1
> Host: httpbin.com
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 201 Created
< server: istio-envoy
< date: Mon, 18 Dec 2023 07:04:06 GMT
< content-type: text/html; charset=utf-8
< access-control-allow-origin: *
< access-control-allow-credentials: true
< content-length: 0
< x-envoy-upstream-service-time: 16
< 
* Connection #0 to host 127.0.0.1 left intact

I’d recommend you to check the header and to make sure the host+route you’re using is correct in the GW+VS.

Note: heads up on the change of this forum moving to Github Discussions: Archive discuss.istio.io by 12/20/2023