<p>managed k8s services like EKS and GKE provide cloud native CNIS.</p>
<p><a href="https://docs.aws.amazon.com/eks/latest/userguide/pod-networking.html" rel="nofollow noreferrer">https://docs.aws.amazon.com/eks/latest/userguide/pod-networking.html</a>
<a href="https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips" rel="nofollow noreferrer">https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips</a></p>
<p>we can install also deploy  service mesh like istio provided CNI in the cluster
<a href="https://istio.io/latest/docs/setup/additional-setup/cni/" rel="nofollow noreferrer">https://istio.io/latest/docs/setup/additional-setup/cni/</a></p>
<p>Now As part of the Istio installation,  if we deploy Istio CNI along with VPC native CNI
how would  the cluster network behave  since both CNI's are running in parallel inside the cluster.</p>

Sai Teja Pakalapati
<p>The Istio CNI plugin actually runs as a chained CNI plugin, which means it is added to the configuration of the existing CNI plugin configured for your cluster.  It should work fine with most CNI plugins.</p>
