Josune Cordoba

> > The prometheus traces shows that the connection_security_policy is set just for the reporter source, but not for the reporter destination: > > I think you mean the opposite....

I think the issue might be originated in the backend, because the sourceCluster is unknown. The lock icon is shown based on the "isMTLS" field, but this is not filled...

I'm no sure what should be the behavior for "Cluster Boxes", it makes no difference in the graph in my environment (I was expecting to remove (cluster-default): 

Sure, we can have a video call to share this view. Thanks, @jshaughn

I've just tested installing Kiali inside the cluster, I can see the same behavior than @jshaughn :   I can investigate further

Thanks, @jshaughn ! I have tested but it didn't work :( But when I run kiali inside the cluster I think is using the same istio instance, right? I was...

> Hmm, I thought that workaround would work, did you see the same issue but with the label `(kubernetes)` instead of `(cluster-default`)? > > Anyway, that warning seems related, cc'ing...

> > 2022-07-28T16:38:16+01:00 WRN Failed to fetch Kiali token when resolving cluster info: open > > /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory > > That's most likely because you started...

> > see this is still empty: > > Yes, that is expected when you set the cluster-name to the default value. In that case Kiali assumes a single-cluster installation....

I finally get the same results, running Kiali in dev mode, outside the cluster:  Steps for the installation: 1. minikube start 2. ./install-istio-via-istioctl.sh -c kubectl 3. ./install-bookinfo-demo.sh -c kubectl...