The train of thought is: if we filter on a cluster, we do want to delete ALL volumes just for that cluster. It doesn't make sense to filter those volumes too if they're not meant to stick around if the cluster who created them is gone.
The current code will find the cluster but also filter the volumes too by name. That's also not possible since Kubernetes PVC Volumes have a random ID as the name (example: pvc-82d40d15-5ce2-418d-bb81-09a0349ec975) so the filtered name won't even be available there.
Description
The train of thought is: if we filter on a cluster, we do want to delete ALL volumes just for that cluster. It doesn't make sense to filter those volumes too if they're not meant to stick around if the cluster who created them is gone.
The current code will find the cluster but also filter the volumes too by name. That's also not possible since Kubernetes PVC Volumes have a random ID as the name (example:
pvc-82d40d15-5ce2-418d-bb81-09a0349ec975) so the filtered name won't even be available there.Related Issue(s)
Fixes #
How to test