Feature Overview (aka. Goal Summary)  

MicroShift allows declarative management of workload using kustomize based manifests, that can be stored on the edge device and are auto-applied on every startup. For a full lifecycle management of solution, there is a need to also auto-delete manifests, e.g. to uninstall no longer components.

Goals (aka. expected user outcomes)

Requirements (aka. Acceptance Criteria):

1. Similiar to the existing folders that can be configure/default to be auto-applied, a similiar structure for auto-delete is established. Same mechanismn, all the folders/files are "oc delete -k ." using kustomize.
2. Errors during delete need to be log as informal only, as this will happen quite frequently on every startup, once the objects are deleted after the initial startup that contained the file.
3. Optionally, if the manifests resides on a writeable filesystem (e.g. is not part of the immutable image), files can be moved/renamed to an "executed/deleted" sub-folder when the "oc delete" was successful. 
4. auto-delete needs to run before the auto-apply, to allow for updates of solutions.
5.  

Questions to Answer (Optional):

none

Out of Scope

n/a

Background

If customers want to create fully self contained images incl. manifests, they needs this to be able to fully lifecycle their application. This is also be needed for microshift internal components that need to remove old/no longer needed components.

Customer Considerations

none

Documentation Considerations

Needs to be documented alongside the existint "auto-apply" docs.

Interoperability Considerations

none