@darnone We should probably make it require a flag to remove manifests so it doesn't happen accidentally. It is documented but I could see that being a surprise and it is destructive so better safe than sorry.

@darnone I think this is a feature we can get done. Another note is that it doesn't destroy the repo, as you can just revert the commit to get everything back. But I also agree that's inconvenient and it makes more sense on uninstall to keep files unless specifically requested.

i made some tests in the code, and i can easily support that. how do you suggest we go about it?
the current default for uninstall is to do it in "gitops" way -

1. delete files from git
2. wait for autopilot-bootstrap app to sync (effectively delete most of the workloads/appprojects/resources from the clsuter)
3. remove all leftovers from the cluster (by different label-selectors)

but just doing the 3rd step would also work and leave the cluster clean.

should i change the default behavior and have an optional flag to do it "gitops"? or should i leave the default, and have the optional flag to run uninstall on cluster only?

i have added a flag of --cluster-only for uninstall, which will basically not do any git operations during uninstall.
it will delete the bootstrap application, which will cascade to delete most resources from the cluster.
afterwards, the code will clean leftovers just like before.

what do you think @todaywasawesome @darnone - would that handle the issue?