You have a single‑zone GKE cluster in us‑central1 running a preview app. To make the app production‑ready with high availability and resilience following Google recommendations, what should you do?

To achieve high availability and resilience for a production-ready GKE application, Google recommends using an Autopilot cluster. Autopilot automatically manages the cluster's underlying infrastructure, including node provisioning, scaling, and upgrades, ensuring optimal resource utilization and resilience across multiple zones by default. Creating an autoscaling zonal cluster with multi-networking is not ideal because it remains zonal, lacking multi-zone resilience. Updating a cluster to convert it to Autopilot is not a direct option; Autopilot clusters are created as such. Adding node locations to an existing cluster only makes it multi-zonal, but it still requires manual management of nodes and doesn't offer the full benefits of Autopilot's automated management for high availability and resilience.