Various traffic issues in Kubernetes

[stevenctl]

Trying to run our existing integration tests on my linux machine in KinD (istio/istio#41633)

• Traffic to a DNS shortname doesn't resolve

I have no name!@captured-v1-54f5cc6f5c-7rl45:/$ curl captured:80     
curl: (6) Could not resolve host: captured

• Traffic to a VIP with a bad port (e.g. 1234 instead of 80) hangs instead of fails (vip + good port succeeds). It does eventually timeout (~60s?), giving the client a "connection reset by peer".

2022-10-26T18:22:29.926979Z  INFO ztunnel::proxy::outbound: accepted outbound connection from [::ffff:10.244.1.12]:34202
2022-10-26T18:22:29.927015Z  INFO ztunnel::proxy::outbound: Proxying to 10.96.18.21:123 using TCP via 10.96.18.21:123 type Passthrough

• Semi-frequent xds stream breakages. Possibly related to the above (I've only seen it immediately after one of these bad attempts)

2022-10-26T18:23:38.889583Z  WARN ztunnel::xds::client: XDS client error: gRPC error (Unknown error): error reading a body from connection: broken pipe, retrying
2022-10-26T18:23:38.889606Z  INFO ztunnel::xds::client: Starting ADS client with 21 workloads

[howardjohn]

DNS shouldn't be impacted, that's odd.

For the hanging - I think this is actually the k8s behavior... since it's just passthrough? We could add a timeout although we probably want to be cautious about making sure that we are modifying underlying Kubernetes behavior too much

[howardjohn]

Is this still an issue?