ComparisonError: manifest generation failed CI/CD Origin: Build & delivery Last updated 25 Oct 2026

Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed

Argo CD could not render the manifests (Helm, Kustomize or plain YAML) for the application, so it cannot compare Git with the cluster and the app shows Unknown.

Exact message you may see ComparisonError: rpc error: code = Unknown desc = Manifest generation errorManifest generation error (cached)Failed to load target state: failed to generate manifest for sourceComparisonError Argo CDkustomize build failed Argo CD
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

The condition message includes the tool's real error. Reproduce it locally: helm template or kustomize build in the same path, with the same values and revision. Common issues are invalid YAML, missing values files, repo access errors and chart dependencies not built.

Common causes

  • Invalid YAML or template error in the chart/overlay
  • Wrong path, targetRevision or values file name
  • Helm dependencies not fetched or private chart repo credentials missing
  • Kustomize base/resource path not found
  • Repo server out of memory or timeout

⚡ Quick fix

  1. Run helm template / kustomize build locally against the same commit
  2. Fix the path, revision and values
  3. Refresh with hard refresh after fixing: argocd app get APP --hard-refresh

Detailed fix by platform

Kubernetes

  1. argocd app get my-app shows conditions; kubectl -n argocd logs deploy/argocd-repo-server shows the render error

Code examples

Reproduce locally

bash
helm template my-app ./chart -f values-prod.yaml > /dev/null
kustomize build overlays/prod > /dev/null
argocd app get my-app --hard-refresh

How to diagnose

  1. Render — Does helm/kustomize work locally?
  2. Path — Correct path and revision?
  3. Repo — Credentials and dependencies OK?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

Cannot find orb — CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist (CI/CD)Cannot find orbConfig compilation failed — CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema (CI/CD)Config compilation fa…Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container exceeded me…error parsing called workflow — GitHub Actions: error parsing called workflow ".github/workflows/ci.yml" -> "org/repo/.github/workflows/build.yml@main": workflow was not found (CI/CD)error parsing called …ImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffNo such DSL method — Jenkins: java.lang.NoSuchMethodError: No such DSL method 'dockerBuild' found among steps (CI/CD)No such DSL methodScripts not permitted to use method — Jenkins: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String toUpperCase (CI/CD)Scripts not permitted…Template file not found — Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template (CI/CD)Template file not fou…Compariso…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.