Describe the bug
We are utilizing Keda as an autoscaler to be based upon current connections. However, when a deployment occurs, all but 1 NGINX Ingress pods are terminated due to replicas: <value> being included within the deployment manifest. This is documented at https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#migrating-deployments-and-statefulsets-to-horizontal-autoscaling

To Reproduce
You can follow the steps listed in this blog post: https://www.nginx.com/blog/microservices-march-reduce-kubernetes-latency-with-autoscaling/

Expected behavior
When doing a deployment, it should respect the rolling strategy as defined, and not include replicas: <value>.

Your environment

• Version of the Ingress Controller - 3.3.1
• Version of Kubernetes - 1.27
• Kubernetes platform (e.g. Mini-kube or GCP) - Azure Kubernetes

Additional context
If there was a way to enable autoscaling without including the built-in hpa