}
                      }
                    }
                  ]
                }
              ],
              "use_original_dst": false,
              "listener_filters": [
                {
                  "name": "envoy.filters.listener.original_dst",
                  "typed_config": {

                        }
                      }
                    }
                  ]
                }
              ],
              "use_original_dst": false,
              "listener_filters": [
                {
                  "name": "envoy.filters.listener.original_dst",
                  "typed_config": {

            "cluster": "PassthroughCluster"
           }
          }
         ],
         "name": "virtualOutbound-catchall-tcp"
        }
       ],
       "use_original_dst": true,
       "traffic_direction": "OUTBOUND"
      },
      "last_updated": "2023-06-20T09:07:41.992Z"
     }
    },
    {
     "name": "virtualInbound",
     "active_state": {

This is where most of Ztunnel's logic lives.

For outbound traffic, we need to first determine where the traffic is destined to.
As Ztunnel operates at L4, we only have the destination IP/port (recovered via `SO_ORIGINAL_DST`).
This may be an IP of a Service, a Pod, or something outside the cluster.
Ztunnel will look up the destination from the [addresses](#address-type) it is configured with.