Using sidecar proxy and mesh gateway to connect VMs to k8s inside one DC


still trying to make the single DC consul with k8s and VMs.

We already have consuls running outside of k8s - and trying to add k8s services to them as a part of service mesh.

The problem is making pods/services in k8s reachable for services from outside of k8s, without creating big bottlenecks - ie federation with mesh gateways for all the traffic.

The current implementation we’re trying is - use external consul servers for k8s.
And set up proxies for services on VMs to use mesh gateway in k8s in remote mode to access services insid k8s.

But for some reason we can’t make it work.

            "destination_name": "static-server2",
            "datacenter": "dc1",
            "local_bind_port": 2222,
            "mesh_gateway": {
               "mode": "remote"

when we set up proxy it still tries to connect directly to the pods ip, disregarding the part about remote mesh gateway.
Is it possible to make it work this way?

12:45:21.846865 IP workload-001.34138 > Flags [S], seq 3142170044, win 64240, options [mss 1460,sackOK,TS val 25196997 ecr 0,nop,wscale 7], length 0