invalid ownership metadata Kubernetes Origin: Platform & cloud Last updated 13 Oct 2026

rendered manifests contain a resource that already exists. Unable to continue with install: ... invalid ownership metadata

Helm wants to create an object that already exists but isn’t labelled as belonging to this release.

Exact message you may see invalid ownership metadatarendered manifests contain a resource that already existsexists and cannot be imported into the current releasemissing key "app.kubernetes.io/managed-by"
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

Objects created manually, by another release or by kubectl apply lack Helm’s app.kubernetes.io/managed-by=Helm label and meta.helm.sh/release-name annotations. Helm refuses to take them over unless you add them (adopt) or delete the object.

Common causes

  • Resource created manually or by another tool before Helm
  • Resource owned by a different release (duplicate names across charts)
  • Migrating from Helm 2 or kubectl-managed manifests

⚡ Quick fix

  1. Adopt it by adding Helm’s label and annotations
  2. Delete the existing object if safe
  3. Rename resources so charts don’t collide

Detailed fix by platform

Kubernetes

  1. bash
    kubectl label  secret db app.kubernetes.io/managed-by=Helm -n app
kubectl annotate secret db meta.helm.sh/release-name=web meta.helm.sh/release-namespace=app -n app

How to diagnose

  1. Owner — Existing labels/annotations
  2. Release — Which release should own it?

🔧 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: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

admission webhook denied the request — Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request (Kubernetes)admission webhook den…AlreadyExists — Error from server (AlreadyExists): ... already exists (Kubernetes)AlreadyExistsanother operation is in progress — Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress (Kubernetes)another operation is …cannot re-use a name that is still in use — Error: INSTALLATION FAILED: cannot re-use a name that is still in use (Kubernetes)cannot re-use a name …CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffCreateContainerConfigError — Kubernetes: CreateContainerConfigError — secret / configmap not found (Kubernetes)CreateContainerConfig…is waiting to start — Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating (Kubernetes)is waiting to startinvalid o…

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.