Replies: 2 comments 1 reply
-
Follow up on this question, would the name of the clusters when we create the KubeConfig entries like mentioned in the documentation need to match what we write on the Mesh Config? istioctl create-remote-secret |
Beta Was this translation helpful? Give feedback.
0 replies
-
Check out this blog I wrote Deciphering Istio Multi-Cluster Authentication & mTLS Connection, which are primary-remote cluster, but the principle should be the same. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am currently testing the MultiCluster setup following the documentation provided in the Istio website:
I have set up two clusters, and on one of them (cluster1), I do not encounter any TLS errors. However, on the second cluster (cluster2), I am encountering the following TLS error:
I have already applied the following configuration on cluster2 using the Istio operator:
I am unsure why this error is occurring. Is it attempting to reach itself (cluster2)? Or could it be related to cluster naming?
Beta Was this translation helpful? Give feedback.
All reactions