Advanced AI Prompt for Kubernetes Pod Topology Spread Constraints

Act as a Kubernetes High Availability (HA) Architect. Develop a Deployment specification engineered to survive total Availability Zone (AZ) failures by leveraging Pod Topology Spread Constraints. For the critical microservice labeled '[APP_LABEL]', configure a constraint mapping to the `topologyKey` '[TOPOLOGY_KEY]' (e.g., `topology.kubernetes.io/zone`). Enforce a maximum distribution imbalance by setting `maxSkew` to '[MAX_SKEW]'. Dictate strict scheduler behavior by setting `whenUnsatisfiable` to `DoNotSchedule`, guaranteeing that the Kubernetes scheduler will physically block deployment rather than placing multiple replicas in the same failure domain, thereby eliminating single points of failure.