Describe the problem/challenge you have

When a node running the stateful pod with Local PV goes out of the cluster, the pod gets into a pending state and remains in a pending state. The administrator or the automated operator will have to run some manual steps to bring the pod back online. The operations to be performed may vary depending on the way storage is connected to the nodes. However, a few options are common across different stateful operators. The general actions to be performed are:

• Run checks to ensure PV is really dead.
  • The node on which PV was provisioned is gone. The node mentioned in the affinity is no longer available in the cluster.
  • The application to which PV was provisioned is deleted. The PV remained in the system due to some failure condition during delete operations.
  • The application is in a state to add new replica (delete old pv/replica and let stateful operator create new pv/replica)
  • other application-specific checks
• Delete the PV and the application PVC/replica
  • If reclaimPolicy is delete, delete the PV
  • If reclaimPolicy is retain, remove references
• Wait for a new PV to be created and run some post operations specific to the application like:

• Run a command/api on application to rebalance

Describe the solution you'd like
A Kubernetes operator that can be launched into the cluster with a ConfigMap(s) that can specify:

• annotations or configuration in the PV spec that uniquely identify the PVs to be acted upon
• enable/disable pre-checks
• enable/disable post-hooks

Anything else you would like to add:
It should be possible to either run this operator independently or embed this controller into other stateful operators.