Background / OverviewIt is possible that when issuing a `konvoy down` command, the operation would fail when it attempts to remove the AWS volumes associated with the cluster. Such error would look like the one below:
AWS volumes with a reclaim policy will be deleted. Error: error destroying cluster: failed to destroy cluster "konvoy-cluster" for provisioner aws: unable to list the persistent volumes: Get "https://konvoy-cluster-6da4-lb-control-698604907.us-west-2.elb.amazonaws.com:6443/api/v1/persistentvolumes": EOFThe problem lies on the fact that one of the operations in the process involves a `konvoy reset` which attempts to list the volumes created with the cluster in order for it to be destroyed. Since the API server is already down, the listing fails and then gives up.
ResolutionRun `konvoy down --skip-clean-kubernetes`.
A manual cleanup of the associated volumes might need to be performed after the operation completes.