'zarf destroy' unable to do anything if 'zarf init' doesn't complete

[YrrepNoj]

Environment

Device and OS: Ubuntu 18.04
App version: v0.15.0
Kubernetes distro being used: None natively, using k3s that Zarf brings with it

Steps to reproduce

1. zarf init --components=k3s --confirm
   • Process crashes or is manually halted before initialization is completed
2. zarf destroy --confirm
3. What ever the issue preventing the initialization is addressed externally
4. zarf init --components=k3s --confirm

Expected result

Step '2' destroys the started up k3s cluster and step '4' stands up a new k3s cluster.

Actual Result

If step '1' was stopped before the zarf state was saved into the registry, then nothing actually happens during the zarf destroy --confirm. This means a k3s cluster is still running on the host and when you try to zarf init again you get an unclear error message about not being able connect to the k8s cluster while still not saving anything to the zarf-state secret so you're not stuck in this loop.

The only way out of this loop is to manually remove the k3s cluster through /usr/sbin/zarf-clean-k3s.sh or some other k3s cleanup script.

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Additional Context