When user removes AWSEBSDriver CR, the operator waits for all PVs provided by the driver to disappear and then it un-installs the CSI driver. But there is no indication that it is happening, especially when a PV still exists. How reproducible: always Steps to Reproduce: 1. Install the CSI driver (i.e., install the operator + create CR) 2. Create PVC + Pod that uses gp2-csi storage class, provided by the driver 3. Delete the AWSEBSDriver CR Actual results: OCP console shows everything as running (Available=true, Progressing=false), and there is no indication why the driver is not uninstalled. Expected results: Some indication that the operator waits for all PVs to be deleted. Question is, what is the right indication. A new condition Terminating = true, with "Waiting for 1 PV that use the driver to be removed"? Or re-use Progressing? But the operator is not progressing, it's stuck at existing PVs.
In 4.6 we do not plan to support un-installation of CSI drivers. AWS EBS CSI driver + its operator is part of the cluster (when running on AWS). We may fix it in 4.5.z, when more serious issue comes around.