I’m trying to achieve canary-style traffic management for applications which are not yet part of the Istio service-mesh but still are in the same k8s cluster. For example:
Pod A in the namespace
non-mesh calls Service B in namespace
mesh which is bound to the pods inside the service mesh. A desired state would be when traffic to these pods is distributed by the rules described in related
Is this possible by Istio’s native facilities?