Marketplace: kwasm provisioning jobs/pods remain after helm delete

[vdice]

This is a placeholder issue that actually isn't specific to the SpinKube Azure Marketplace chart but I wanted to document pending a potential fix upstream* (in the kwasm-operator, or in the future, runtime-class-manager project).

The kwasm/rcm provisioning job(s) and their corresponding pod(s) persist even after deleting the helm release for this chart. As a result, when the SpinKube Marketplace extension is uninstalled, the same behavior will be seen.

*A potential fix could be to allow configuration of a TTL for the provisioner job (eg spinkube/runtime-class-manager#199)

[vdice]

#29 addresses this for the marketplace chart.