Marc Boorshtein

> but could you test with an older version of Kiali to ensure that something hasn't changed recently? v1.65 would be good. It looks like the breaking change was part...

Went through the commits comparing the 1.74.1 tag 1.75.0 and there are only change that appears to be the culprit (or really related at all) is: https://github.com/kiali/kiali/commit/45d72534b0556c0425f52a1488811eb372c92e43 But this only...

Tried backing out https://github.com/kiali/kiali/issues/7125#issuecomment-1957920303 locally and testing, same result as 1.75.0.

@nrfox - So i totally messed up my testing. I was checking the Applications tab and I think you're right about just the wrong version. I noticed that the configs...

Sorry, this fell off the map, though i do need to revisit. I disagree @jshaughn that the functionality is acceptable as is. The problem with discovery selectors is they're static...

> meaning for each Istio service mesh within the cluster, there is one Kiali. I'd argue that's a really narrow definition and is prone to security issues. It's also not...

> Well, I can say without question that Kiali since day one has been designed (and implemented) to support/manage/observe one and only one Istio Service Mesh. I'm not saying anything...

@plainlystated did you ever get synology's csi provider working? I'm getting the exact same error. @MansM I do have iscsi installed: ``` talosctl get extensions --nodes 192.168.2.231 NODE NAMESPACE TYPE...

@jdani I did! I don't know about the TueNAS CSI but this is what I did to get it working with Synology - https://github.com/mlbiam/Kargo/blob/main/ISCSI.md

+1 that a vcluster's SA tokens expire after 10 years opens up not only the vcluster, but also any services a vcluster relies upon - such as an external Vault...