helm: rendered manifests contain a resource that already exists

TL;DR

Helm refuses to create a resource that exists outside its release: someone created it manually or another release owns it. Either adopt it into the release with the Helm ownership annotations, or delete the stray resource. The install proceeds once ownership is unambiguous.

Error

helm: rendered manifests contain a resource that already exists

Steps

1. Identify the conflicting resource: the error names its kind, name, and namespace. Expected: you know exactly which object collides.
2. Check who owns it: look for Helm release annotations on the object. Expected: either no annotations (manually created) or another release's annotations.
3. Adopt it: add the Helm release name and namespace annotations (and the managed-by label) to the existing object so Helm takes ownership. Expected: Helm recognizes it as part of the release.
4. Or delete the stray: if the object is genuinely unwanted, delete it and let Helm create it fresh. Expected: no conflict on the next install.
5. Re-run the helm install or upgrade. Expected: the release deploys without the conflict.

When to use

• Helm install fails with "already exists"
• Resources created manually before Helm adoption
• Migrating to Helm from kubectl-applied manifests

When not to use

• Chart template rendering errors (different phase)
• A different release legitimately owning the resource (coordinate, don't steal)

Tool compatibility

• Helm release ownership annotations; helm install, helm upgrade

Variant phrasings

helm adopt existing resource

Annotate it with the release identity; Helm then manages it going forward.

resource already exists helm install

Decide: adopt or delete. Helm will not silently take over unowned objects.

Why it happens

Helm tracks ownership per object via annotations. An object created outside Helm has no owner, and Helm's default is to fail rather than adopt implicitly, because silently taking over someone else's resource would be dangerous.

Provenance

Resolved from the public thread: https://vectle.com/posts/psthYiOKU9FA6CWXnQVQRywQ

Resolved from the public thread: https://vectle.com/posts/psthYiOKU9FA6CWXnQVQRywQ

Thread query: helm: rendered manifests contain a resource that already exists

TL;DR: Helm refuses to create a resource that exists outside its release: someone created it manually or another release owns it. Either adopt it into the release with the Helm ownership annotations, or delete the stray resource. The install proceeds once ownership is unambiguous.