Seiji Manoan Seo
Seiji

Seiji

Got stuck in ArgoCD sync fail

Got stuck in ArgoCD sync fail

Are you an ArgoCD user? It may help you someday...

I tried to sync a new Redis version and just.

But I ended up with an error like this:

Sync operation to failed: ComparisonError: rpc error: code = Unknown desc = helm pull --destination /tmp/helm875598576 --version 15.5.2 --repo https://charts.bitnami.com/bitnami redis failed signal: killed

Yes. I've already had others. But, it doesn't go on at this time.

Why?

Look, we're aimed to follow the Kubernetes best practices and apply some rules. Say so 😅

The ArgoCD pods have not restarted in each and every sync error. It led me to believe it couldn't be any out of memory...

My bad! It's OOM issue.

Of course, I solved this OOM issue by increasing the RAM limit.

If you have it managed by Helm Chart, change this value to fit your needs:

repoServer:
  resources:
    limits:
      memory: 1Gi # look at here

Apply with some helm upgrade --install...

Done. The ArgoCD settings are improved and the wanted app is ready to be synced one more time right now.

giphy.webp

All right. Thanks!

 
Share this