A development team at your company has created a dockerized HTTPS web application. You need to deploy the application on Google Kubernetes Engine (GKE) and make sure that the application scales automatically. How should you deploy to GKE?

The correct approach for deploying a scalable HTTPS web application on GKE involves using both Horizontal Pod Autoscaler (HPA) and cluster autoscaling. HPA automatically scales the number of pods based on metrics like CPU utilization, ensuring the application can handle varying loads. Cluster autoscaling then adjusts the number of nodes in the GKE cluster to accommodate the pod scaling, preventing resource exhaustion. An Ingress resource is the standard and most flexible way to expose HTTPS services in GKE, providing advanced traffic management, SSL termination, and integration with Google Cloud's load balancing capabilities. Using a Service of type LoadBalancer directly exposes a network load balancer, which is less feature-rich for HTTP/S traffic than an Ingress. Enabling autoscaling on the Compute Engine instance group directly, without GKE's cluster autoscaler, bypasses Kubernetes's native scaling mechanisms and is not the recommended way to manage GKE node scaling.