Closed israel-hdez closed 5 years ago
Multi-cluster seems to be partially broken in the coming Istio 1.3 release. Reported in https://github.com/istio/istio/issues/16890.
UPDATE: class A 127.* IP range cannot be used on Istio 1.3. This was the issue. Istio docs are updated with a new suggested IP range.
Reducing scope of this issue only to the replicated control plane case. The shared control plane case is being tracked in https://github.com/kiali/kiali/issues/1833.
When you have istio spanning multiple Kubernetes clusters, kiali will only list namespaces that live on the cluster where Kiali runs.
There is a flag istio/multicluster. If that is true, we should look for a secret that contains kube configs for the other clusters and use those to talk to the remote clusters and pull their data in.
the main istio control plan can be informed that there are other cluster federated by the fact that there are secrets with the following label: istio/multiCluster=true
The content of the secret is a kubeconfig file that can be used to connect to the other cluster. There can be multiple of such secrets.
Issue migrated from Jira: https://issues.jboss.org/browse/KIALI-1797 https://issues.jboss.org/browse/KIALI-2584 (most details here)
--
Tasks for replicated control plane setup (previously known as multiple control plane):