Apparently, kcli delete vm automatically detects if a VM is part of a Kubernetes/OCP cluster and automatically runs oc delete node upon deletion.
This is useful 95% of the cases, but there are concrete situations where it is not (e.g. decomisioning a failing control plane node while the etcd cluster doesn't have quorum). So it would be useful to have an opt-in flag like --skip-kube-node-deletion that skips this logic and just removes the VM (it would be then up to the user to clean the nodes once etcd quorum is later restored).
Of course there may be workarounds (like just messing with virsh), but it would be ideal to just have this in kcli directly.
Apparently,
kcli delete vmautomatically detects if a VM is part of a Kubernetes/OCP cluster and automatically runsoc delete nodeupon deletion.This is useful 95% of the cases, but there are concrete situations where it is not (e.g. decomisioning a failing control plane node while the etcd cluster doesn't have quorum). So it would be useful to have an opt-in flag like
--skip-kube-node-deletionthat skips this logic and just removes the VM (it would be then up to the user to clean the nodes once etcd quorum is later restored).Of course there may be workarounds (like just messing with virsh), but it would be ideal to just have this in kcli directly.