As part of the introduction of #1458, evict was chosen over delete explicitly to honour PDBs.

This causes issues and confusion when distinct configuration is desired for distinct use cases i.e. a low maxUnavailable PDB control normal operation voluntary disruption like Karpenter and node draining. A high maxUnavailable is used to control the desired deployment rate (usually in conjuction with a multi AZ setup). In this case PDB will win and prevents a fast roll-out.

Kubernetes 1.35 is bringing native maxUnavailable for statefulsets which if integrated here will solve the issue. It could be a long time coming for users to get to that version.

I'd like to float the idea of making the use of evict/delete configurable when maxUnavailable is set