Hello,this (same network, multi primary).
I can successfully ping curl IPs from one cluster to a pod in another cluster.
I am able to see the pods/DNS endpoints urls from both clusters ( istioctl --context $CTX_CLUSTER1 proxy-config endpoint sleep-dd98b5f48-djwdw.sample | grep helloworld )
However, load balancing from the verify step doesn’t work: it shows only v1. Also, running curl using the DNS doesn’t work and running nslookup shows just the resolve.conf.document up to date / needed to follow these steps and add ISTIO_META_DNS_CAPTURE? any idea what should I check?
opened 04:06PM - 24 Aug 21 UTC
area/networking
feature/Multi-cluster
**Bug description**
Hello,
I installed Istio multi cluster using this doc: http… s://istio.io/latest/docs/setup/install/multicluster/multi-primary/ (same network, multi primary).
I can successfully ping curl IPs from one cluster to a pod in another cluster.
I am able to see the pods/DNS endpoints urls from both clusters (`istioctl --context $CTX_CLUSTER1 proxy-config endpoint sleep-dd98b5f48-djwdw.sample | grep helloworld`)
However, load balancing from the verify step in this doc https://istio.io/latest/docs/setup/install/multicluster/verify/ doesn't work: it only shows v1. Also, running curl using the DNS doesn’t work and running nslookup shows just the resolve.conf.
Is this document https://istio.io/latest/docs/ops/configuration/traffic-management/dns-proxy/ up to date / needed to follow these steps and add ISTIO_META_DNS_CAPTURE? any idea what should I check?
[ ] Docs
[ ] Installation
[ x ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
**Expected behavior**
I would expect curl to return randomly v1 and v2 with load balancing as described in the multicluster install verification step.
**Steps to reproduce the bug**
Run two EKS clusters, with VPC peering.
Install two istio as mentioned in this tutorial: https://istio.io/latest/docs/setup/install/multicluster/multi-primary/
**Version** (include the output of `istioctl version --remote` and `kubectl version --short` and `helm version --short` if you used Helm)
1.11.0
**How was Istio installed?**
istioctl
**Environment where the bug was observed (cloud vendor, OS, etc)**
AWS
Additionally, please consider running `istioctl bug-report` and attach the generated cluster-state tarball to this issue.
Refer [cluster state archive](http://istio.io/help/bugs/#generating-a-cluster-state-archive) for more details.
2 Likes
xyzyy
September 7, 2021, 2:05am
2
I have same issue, does anybody resolve it?