openshift-docs/microshift_running_apps/microshift-deleting-resource-manifests.adoc

:_mod-docs-content-type: ASSEMBLY
[id="microshift-deleting-resource-manifests"]
= Deleting or updating Kustomize manifest resources
include::_attributes/attributes-microshift.adoc[]
:context: microshift-deleting-resource-manifests

toc::[]

{microshift-short} supports the deletion of manifest resources in the following situations:

* Manifest removal: Manifests can be removed when you need to completely remove a resource from the node.
* Manifest upgrade: During an application upgrade, some resources might need to be removed while others are retained to preserve data.

When creating new manifests, you can use manifest resource deletion to remove or update old objects, ensuring there are no conflicts or issues.

[IMPORTANT]
====
Manifest files placed in the `delete` subdirectories are not automatically removed and require manual deletion. Only the resources listed in the manifest files placed in the delete subdirectories are deleted.
====

include::modules/microshift-manifests-deletion-overview.adoc[leveloffset=+1]

[id="microshift-examples-of-usecase_{context}"]
== Use cases for manifest resource deletion

The following sections explain the use case in which the manifest resource deletion is used.

include::modules/microshift-manifests-removal-scenario-rpm.adoc[leveloffset=+2]

include::modules/microshift-manifests-removal-scenario-ostree.adoc[leveloffset=+2]

include::modules/microshift-manifests-upgrade-scenario-rpm.adoc[leveloffset=+2]

include::modules/microshift-manifests-upgrade-scenario-ostree.adoc[leveloffset=+2]

[role="_additional-resources"]
== Additional resources
* xref:../microshift_running_apps/microshift-applications.adoc#applications-with-microshift[Using Kustomize manifests to deploy applications]