Currently, when the controller finalizes an EtcdCluster, it just directly removes each EtcdMember’s finalizer, so the Kubernetes deletes it automatically. But all resources (PV/PVC, certificate etc.) owned by the EtcdmMember aren’t cleaned up. We should clean up all the resources owned by an EtcdMember before removing its finalizer.
We should reuse the implementation (source code) as the terminating case, triggered by either scale in or users manually removing an EtcdMember.
Currently, when the controller finalizes an EtcdCluster, it just directly removes each EtcdMember’s finalizer, so the Kubernetes deletes it automatically. But all resources (PV/PVC, certificate etc.) owned by the EtcdmMember aren’t cleaned up. We should clean up all the resources owned by an EtcdMember before removing its finalizer.
We should reuse the implementation (source code) as the terminating case, triggered by either scale in or users manually removing an EtcdMember.