Your company has an application running as a Deployment in a Google Kubernetes Engine (GKE) cluster. When releasing new versions of the application via a rolling deployment, the team has been causing outages. The root cause of the outages is misconfigurations with parameters that are only used in production. You want to put preventive measures for this in the platform to prevent outages. What should you do?

Configuring liveness and readiness probes in the Pod specification is the most effective preventive measure. Readiness probes ensure that a Pod only receives traffic when it's fully ready to serve requests, preventing traffic from being routed to an uninitialized or misconfigured application. Liveness probes detect if an application within a Pod is unhealthy (e.g., deadlocked) and automatically restart the container, ensuring continuous availability. This directly addresses outages caused by misconfigurations during deployments by preventing unhealthy Pods from serving traffic. Health checks on the managed instance group are for the underlying VMs, not the application within GKE. A Scheduled Task to check availability is reactive, not preventive. An uptime alert in Cloud Monitoring is also reactive, notifying you after an outage has occurred, rather than preventing it.