This is continuation of STOR-2277, which introduced fast restart as upstream alpha feature.

Epic Goal

Incorporate the upstream alpha change in OCP. I.e. run the CSI sidecars of a CSI driver with the feature gate enabled.

Why is this important? (mandatory)

This will dramatically reduce time to start a replacement CSI sidecar, for example during a cluster upgrade. Right now, the new sidecar needs to wait for the old lease to expire (2-3 minutes), but they could start instantly.

In addition, this will provide us data for upstream that the feature is useful & did not bring any regressions.

Scenarios (mandatory) 

1. As OCP / Kubernetes developer / user, I can restart a CSI sidecar, e.g. with a new log level, and I can see the sidecar to start immediately working, without waiting 2 minutes for leader election, so I can debug my cluster faster.
2. As OCP cluster admin, I can upgrade my cluster without 2-3 minute gap in volume provisioning / attachment during the upgrade, caused by the attacher / provisioner sidecars waiting for the old leader lease to expire.

Contributing Teams(and contacts) (mandatory) 

• Development - 
• QE - 

Open items

• Which CSI driver(s) to choose?
• Have it opt-in or opt-out or non-configurable?