Scale down StatefulSet to 0 before deleting to terminate pods gracefully

[anveshreddy18]

How to categorize this issue?

/area robustness
/kind enhancement

What would you like to be added:

Upon deletion of an Etcd, the current deletion flow for StatefulSet attempts to delete it directly as follows :

etcd-druid/internal/component/statefulset/statefulset.go

Lines 157 to 160 in c73cbf9

	func (r _resource) TriggerDelete(ctx component.OperatorContext, etcdObjMeta metav1.ObjectMeta) error {
	objectKey := getObjectKey(etcdObjMeta)
	ctx.Logger.Info("Triggering deletion of StatefulSet", "objectKey", objectKey)
	if err := r.client.Delete(ctx, emptyStatefulSet(etcdObjMeta)); err != nil {

However, as per the Kubernetes statefulset limitations, it says

StatefulSets do not provide any guarantees on the termination of pods when a StatefulSet is deleted. To achieve ordered and graceful termination of the pods in the StatefulSet, it is possible to scale the StatefulSet down to 0 prior to deletion

In order to avoid the scenario of orphaned pods and to finish the deletion of statefulset gracefully, it would be better if sts is scaled-down before deleting it.

Why is this needed: