# Why can helm uninstall in Helm 4.3 leave behind an object listed in the release's stored manifest?

Helm, Hard (Expert), Troubleshooting. https://k8wiz.com/uquiz/why-can-helm-uninstall-in-helm-43-leave-behind-an-object-listed-in-the-releases-stored-manifest

- A. Its Helm ownership label or annotations don't match this release
- B. It was changed with kubectl edit after the last helm upgrade ran
- C. It lives in a namespace other than the namespace of the release
- D. It was created by a template that also defines a pre-install hook

**Answer:** Its Helm ownership label or annotations don't match this release

**Explanation:** Since 4.3.0, uninstall fetches each object and deletes it only if it has app.kubernetes.io/managed-by: Helm and meta.helm.sh/release-name and release-namespace annotations matching the release. Objects adopted by another release, or whose ownership can't be read (for example without get permission), are skipped and listed. The check compares the release-namespace annotation, not the object's own namespace.