PodDisruptionBudget enforcement during StatefulSet ordinal deletion in node drain operations?

A StatefulSet scales down by deleting its highest‑ordinal pods, and a node drain may issue a direct DELETE request that bypasses the eviction subresource.

PodDisruptionBudget evaluates minAvailable or maxUnavailable against the current count of ready pods, but the definition of ready can differ for pods that are terminating yet still counted as available, and behavior may vary across Kubernetes versions or be affected by third‑party controllers.

Does the StatefulSet controller honor PDB constraints when processing a scale‑down request? If the highest‑ordinal pod would violate the PDB, does the operation block or proceed? Can a direct DELETE request bypass the PDB enforcement during node drain?