I am trying to implement blue/green deployment using Istio virtual services and destination rules. Seems like I can make it work when calling from outside the cluster, but when a pod calls another pod the requests are balanced on both blue and green instances. All the pods involved have the Envoy sidecar.

I installed istioctl on my Mac and am trying to run this command from the terminal

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

In ISTIO VirtualService and DestinationRule Not behaving properly, find the manifest below,
when trying to curl my service its distributing traffic to both v1 and v2 pod even after mentioning v1 only in virtual service

I’m running a local Kubernetes cluster with Istio installed onto it. I have one authorization server running in a deployment in the namespace “authserver”, and one resource server running in a deployment in the namespace “resourceserver”. Each of these deployments have a ClusterIP service in front of them to expose them internally to the cluster.

We are planning to migrate to our app to kubernetes. would like to do a lest possible changes as possible. Is there a way to map internal DNS abc.xyz to abc-xyz.default.svc.cluster.local. if the app calles abc.xyz it abc-xyz.default.svc.cluster.local.