This might be an edge case, but when switching from a WasmCloudHostConfig that has daemonset: true in its schedulingOptions to a regular Deployment-based WasmCloudHostConfig, the DaemonSet does not get cleaned, up. The same is true vice-versa.
When deleting the WasmCloudHostConfig, it does however delete all created DaemonSets and Deployments as the owner references are correctly set.