In progressive canary, when we do the deployment, the HPA splits based on the percentage defined on the live traffic.

But in standard Canary, it just creates a replica of the same HPA resources, without checking the percentage. As a result, if someone has defined 1 replica or any replica percentage, it is not respecting that and is creating a default HPA.

We have a higher minimum value in the HPA, due to which the number of instance we are defining or the percentage is not getting respected.

Link to the doc how it works in progressive canary - https://developer.harness.io/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/kubernetes/kubernetes-executions/create-a-kubernetes-progressive-canary-deployment#horizontal-pod-autoscaler-and-pod-disruption-budget

We need similar in the standard as well.