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

**Code:** `invalid ownership metadata` · **Category:** Kubernetes · **Seen on:** Kubernetes

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

## 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?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/kubernetes/helm-invalid-ownership-metadata)