Closed sundongmin closed 4 years ago
If you run istioctl pc listener org-api-599588fb86-l5fzn -n dev --port 6379
, you can see istio generates one listeners per redis instance.
It seems you met the known issue with automtls. For more context #21964
The workaround is disable mtls explicitly with destinationrule.
DestinationRule.trafficPolicy.Tls == DISABLE https://github.com/istio/istio/issues/21964#issuecomment-596382298
Closing as a duplicate of https://github.com/istio/istio/issues/21964 as this seems the same issue and has not had any updates for quite some time
Bug description In kubernetes, I hava two nameapace, a called
dev
, another calledcitest
. I hava a java application run indev
, and need to connect to external redis cluster(useAmazon ElastiCache
), whencitest
has a statefulset redis cluster(no sidecar
), then java applicatioin cannot connect to external redis clusterExpected behavior
0.0.0.0_6379
, but I don't understand why all the tcp traffic route to theredis-cluster.citest.svc.cluster.local
, Can anyone tell me why?Steps to reproduce the bug
citest
), deploy a statefulset redis clusterHere's log from that time
Version (include the output of
istioctl version --remote
andkubectl version
andhelm version
if you used Helm)How was Istio installed? istioctl
Environment where bug was observed (cloud vendor, OS, etc) kubernetes clusters with kubeadm on aws ec2