Domain generated for isolated routing responds with 404

[ostrolucky]

Describe the bug
I've created isolated routing via vscode, but domain that extension gives back does not seem to be routed to a pod

❯ curl -k https://gostrolu-7483.data-center-compliance.eqs.dev/api/health_check -v
*   Trying 10.10.59.222:443...
* Connected to gostrolu-7483.data-center-compliance.eqs.dev (10.10.59.222) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=eqs.dev
*  start date: Feb 13 00:00:00 2023 GMT
*  expire date: Dec  5 23:59:59 2023 GMT
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
* using HTTP/2
* h2 [:method: GET]
* h2 [:scheme: https]
* h2 [:authority: gostrolu-7483.data-center-compliance.eqs.dev]
* h2 [:path: /api/health_check]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* Using Stream ID: 1 (easy handle 0x131014200)
> GET /api/health_check HTTP/2
> Host: gostrolu-7483.data-center-compliance.eqs.dev
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/2 404
< server: awselb/2.0
< date: Fri, 08 Sep 2023 21:01:46 GMT
< content-type: text/plain; charset=utf-8
< content-length: 0
<
* Connection #0 to host gostrolu-7483.data-center-compliance.eqs.dev left intact

Mention the platform you are using
vscode

[hsubramanianaks]

@ostrolucky Gabriel is this still happening or did you find a work around for this one? Honestly sounds like this issue doesn't belong to bridge to kubernetes, might be related to your local machine. Please let me know. Thank you.