I wouldn't expect service meshes to be like ingress controllers.
An ingress controller is handed a list of routing rules (Ingress objects) based upon hostname, path, & occasionally port and sends all traffic from outside to the internal services (or pods) accordingly.
A service mesh is usually going to be a sidecar to every pod in the scope (namespace I think usually) you apply it to and all traffic will go through the sidecar. This can allow inspection, encryption, authentication and/or authorization, logging, address translation, and probably other things that don't jump to mind. What specifically you have it do is up to you, though.