thoughtworks / metrik

An easy-to-use, cross-platform measurement tool that pulls data out of CD pipelines and analysis the four key metrics for you.
MIT License
354 stars 87 forks source link

When using persistent volume (Azure File Share/ Azure Disk) on AKS Cluster, the application failed to read the Git hub data. #101

Closed mmsajidcloud closed 2 years ago

mmsajidcloud commented 2 years ago

Hello Awesome Team,

Describe the bug

When using persistent volume (Azure File Share/ Azure Disk) on AKS Cluster, the application failed to read the Git hub data, it kept on synchronizing but never loaded any data.

However if we deploy the application on AKS, with out any external volume mount, it works fine.

To Reproduce

SetUp

  1. Create a Storage class (Azure File Share) on AKS Cluster

  2. Create a PVC (Persistent Volume Claim)

  3. Create a deployment and mount the /data/db on the above created PVC

  4. Create a load balancer service for accessing the application.

  5. Access the application using load balancer IP,

  6. Create a new project and configure with GITHUB repo using PAT tokens.

Expected behavior

The application would have loaded the GITHUB data and display the charts.

Screenshots

image

image

Cluster Information

K8s Version : 1.20.7 Cloud Provider : Azure Persistent Volume : Azure File Share / Azure Disk

mba484 commented 2 years ago

Any inputs on this will be appreciated

hyrepo commented 2 years ago

Hi @mmsajidcloud and @mba484, I think this may be caused by some data writing issue. After data sync, data will be written into the database, and it will be retrieved for calculation. So If data can't be written into DB then there will be no data shown in the page.

I'm not sure what happened since we don't have AKS, but you may try to check the access control of the PVC as mentioned in here, the access issue happens sometimes.

mba484 commented 2 years ago

Hi @hyrepo,

Thanks for coming back, we have managed to fix this by giving permission in the persistent storage class.

image

hyrepo commented 2 years ago

Hi @mba484 , glad to hear that, closing this issue