Hello,
I attempted to deploy a YugabyteDB within a Kubernetes cluster as part of a multi-cluster setup. After the deployment is up and running, I tried to access the Yugabyted UI from the LoadBalancer’s external IP. The dashboard couldn’t access any metrics or data about the cluster. Looking at the network tab shows that some HTTP requests return a 500 error. The full error message is shown in the image below.
YugabyteDB Master UI works just fine, and I was able to see all of the cluster’s information. So this problem isolates the Yugabyted UI component that’s broken. I tried to turn off the Istio Compatibility, and somehow Yugabyted UI is back up and running, and now it can fetch the metrics and data it needs.
I tried to deploy YugabyteDB again, but for a single-cluster setup, using the minimal change in the Helm value by turning on the istioCompatibility. The output is still the same, Yugabyted UI is unable to fetch any data with error 500.
For a bit of context, the ysql is working fine, and I managed to create the service mesh as I intended to do. But I also wanted to have a nice dashboard for me to check the cluster metrics such as latency and IO, without building my own Grafana dashboard.
Edit:
I have created a GitHub issue based on this problem [yugabyted] Yugabyted UI Service can’t fetch any data when Istio is enabled #29880