v2.0.1 : repo-server helm manifest build is failing

[Greyeye]

kubechecks bin version: v2.0.1
kubechecks chart version: v0.5.2
argo-cd version: 1.12.3

issue
The application manifest (chart.yaml) with dependencies fails to build helm manifests.
The issue does not occur for all the time but only happen when the kubechecks needs to build multiple apps manifests together.

possibly related to issue from argo-cd
argoproj/argo-cd#18122

sample chart.yaml

apiVersion: v2
version: 1.0.0
name: external-dns
dependencies:
  - name: external-dns
    repository: https://charts.bitnami.com/bitnami
    version: 8.3.5

error

2024-12-23 00:04:49.012Z argocd-repo-server-77f669ddfd-88g5c argocd-repo-server time="2024-12-23T00:04:49Z" level=error msg="`helm dependency build` failed exit status 1: Error: no cached repository for https:--charts.bitnami.com-bitnami found. (try 'helm repo update'): error loading /helm-working-dir/repository/https:--charts.bitnami.com-bitnami-index.yaml: empty index.yaml file" execID=1f910
2024-12-23 00:04:49.015Z argocd-repo-server-77f669ddfd-88g5c argocd-repo-server time="2024-12-23T00:04:49Z" level=error msg="finished streaming call with code Unknown" error="`helm dependency build` failed exit status 1: Error: no cached repository for https:--charts.bitnami.com-bitnami found. (try 'helm repo update'): error loading /helm-working-dir/repository/https:--charts.bitnami.com-bitnami-index.yaml: empty index.yaml file" grpc.code=Unknown grpc.method=GenerateManifestWithFiles grpc.service=repository.RepoServerService grpc.start_time="2024-12-23T00:03:54Z" grpc.time_ms=54103.344 span.kind=server system=grpc

[djeebus]

I suspect this is due to a missing Chart.lock file and charts subfolder. helm dep build won't pull repos that aren't added to helm (or in this case, argocd), but for unknown reasons helm dep up will. Just to verify, would you mind running helm dep up in that folder, committing the files it generates, and see if it still has issues generating the resources?

[Greyeye]

@djeebus added charts folder and chart.lock to the branch, unfortunately, it still fails
https://gitlab.com/zapier/team-sre/kubernetes-cluster-bootstrap/-/merge_requests/1164
I also check if we're seeing some weird OOM as per other issue received, but all our argo-cd-repo-server pods are 4Gi limit as well.