things like layer 7 control, you can say - "don't allow HTTP GET on /supersecret". Also, Isito is gRPC aware
Istio offers much more, but as far as anything but coarse-grained "this service will never need to talk to this other service" access control, I'd still much rather write the logic in the code where it has access to a lot more domain knowledge.
Personally, I think that Istio is overly complex but then so is k8s :)
[1] https://kubernetes.io/docs/concepts/services-networking/netw...