[Question][Helm Chart deployment] Unable to connect to MySQL database through Grafana

[gauravagerwala]

Question

I created a new deployment using Helm charts (with ingress) and am unable to connect Grafana to the mySQL datasource.

The pipelines ran successfully and ingested data into the database. (verified by checking the data on the cluster)

Screenshots

## Additional context When I attempted a similar deployment with NodePort I was able to connect succesfully.

[klesh]

Can you scroll up to the top and check the mysql host setting?

[gauravagerwala]

The host on this page is pointing to localhost:3306

I attempted to update this but that does not change the host. Note the banner that says the config cannot be modified.

On the cluster I see a config map that defines the URL as devlake-mysql:3306. This matches with the name of the ClusterIP service for mysql on the cluster.

[klesh]

Which version was it? Stable or development?

[klesh]

I tried the stable version v1.0.2 on Minikube and observed the same result.
After some digging, it seems the issue might be related to #337.

That said, my knowledge of Helm charts is limited, so I wonder if @kahirokunn could help diagnose the problem?

PS: I also tried deploying the development version but ran into another issue, similar to grafana/helm-charts#752. I’m not sure if this is specific to minikube on my local machine or if it could also affect production deployments.

[kahirokunn]

Could you please share the exact Helm values you used for installation, along with the commands you ran and how you accessed Grafana? That way I can fully reproduce the issue on my side.

[kahirokunn]

@klesh I think this fixed it. 🙏
apache/devlake-helm-chart#353

[klesh]

@kahirokunn Thank you very much for the quick fix. Much appreciated

[gauravagerwala]

@kahirokunn any advice on how I can patch my environment directly?
(While we wait for the new helm release to be created)

I added the variables directly to the grafana pod, but that did not refresh the variables on the dashboard itself

[gauravagerwala]

@kahirokunn I also don't see a configmap names devlake_mysql_auth_config in my cluster.

The configmap with the variables defined is devlake-config

[kahirokunn]

In the meantime, using an older version of helm chart works fine.

[gauravagerwala]

I was able to locate the issue. The grafana deployment was not referencing devlake-config configmap
Once I added this configmap to the deployment, the grafana pod was able to pick up the required env variables.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.