Description
Describe the bug
A cursory look of the source does not seem to indicate that the Kubernetes Eviction API is used at all by Lens. This leads me to believe that Deployments and Pods are when they are deleted are so without respect to Pod Disruption Budgets. Actions from the UI I would consider to be voluntary and that has implications based on the documentation.
See this section: https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets
Cluster managers and hosting providers should use tools which respect PodDisruptionBudgets by calling the Eviction API instead of directly deleting pods or deployments.
Expected behavior
Utilize the Eviction API for DELETE requests
Screenshots
If applicable, add screenshots to help explain your problem.
All Links:
https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-budgets
https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/#eviction-api
https://kubernetes.io/docs/concepts/scheduling-eviction/api-eviction/
Reference: https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.24/#create-eviction-pod-v1-core