Hpa not scaling up replicas to spec. There is not events found in hpa Here's the HPA in YAML: apiVersion: autoscaling/v2beta2 kind: HorizontalPodAutoscaler metadata: name: ping-adapter spec: sca. Horizontal scaling means that the response to increased load is to deploy more Pods. In the cluster there is a single deployment called app on which I deployed a HPA with this command kubectl autoscale deployment app --cpu-percent=50 --min=1 --max=10 And until here it's fine, it seems it scale up just fine. How Sep 21, 2023 · I have app-1 deployment and I have configured HPA for it. I've set the target CPU utilization at 50%, with a stabilization window of 0. Learn more! Oct 28, 2025 · HorizontalPodAutoscaler Walkthrough A HorizontalPodAutoscaler (HPA for short) automatically updates a workload resource (such as a Deployment or StatefulSet), with the aim of automatically scaling the workload to match demand. As you found the reason please provide an answer to your question to help the community with similar issues. Jun 3, 2024 · Error: The HPA might scale pods up or down too quickly, causing frequent and unnecessary scaling actions. #79035 max-rocket-internet changed the title HPA scales to maximum even though metric is under target HPA doesn't scale down to minReplicas even though metric is under target on Jun 17, 2019 Hello Kubernauts, I have a cluster deployed with AKS-Engine. I’ll walk you through the Mar 5, 2021 · By the formula in the HPA documentation, there must be at least a queue size of 10 to scale up from 1 pod to 2. Reduce the load i. io Sep 21, 2024 · What happened? I'm using the HPA to scale my pods based on CPU usage. Nov 5, 2021 · What happened? Kubernetes HPA not auto scaling when target utilization reached. , the value of the other metric so that the HPA kicks in and scales up the pods to the max replica count. Create a custom-metric-based HPA that uses two metrics among which the value of one is undefined. Shorter windows make HPA more responsive, but may cause instability. Mar 3, 2024 · 1. Kubernetes inherently supports CPU and memory metrics, but leveraging custom and external metrics introduces a nuanced approach to scaling, allowing for more precise control based on the actual demands of your application. Oct 24, 2019 · I have created HPA for my deployment, it’s working fine for scaling up to max replicas (6 in my case), when load reduces its scale down to 5 but it supposed to come to my original state of replicas Jun 6, 2019 · HPA scales up with no reason / blank reason #78712 Fix HPA feedback from writing status. replicas. Nov 21, 2020 · In Kubernetes HPA doesn't scale down after decreasing the loads I note that, if you specify multiple metrics, the largest replica count for any metric determines the scaling value. e. Is it consistently staying above that level for long enough for HPA to notice? See full list on kubernetes. Problem is that when the cpu utilization goes to 0%, the HPA doesn't downscale: NAME REFERENCE TARGETS MINPODS Jan 18, 2025 · However, configuring the HPA to handle scaling up and scaling down events efficiently while avoiding unnecessary resource churn is crucial for production environments. Solution: Adjust the targetAverageUtilization or targetAverageValue in the HPA configuration to smooth out scaling decisions. May 23, 2025 · In this post, I’ll explain why the Kubernetes Horizontal Pod Autoscaler (HPA) might not be scaling your pods — even if it looks like everything is correctly set up. the value of the metric, it will be stuck at a random value. Feb 16, 2024 · Example In the scenario where an HPA is set to scale up when memory average utilization reaches 85%, and your workload consumes 93% of pod memory, the HPA does not trigger scaling up. May 22, 2025 · By default, HPA evaluates every 15 seconds, but it helps to define scale-up and scale-down delay windows to prevent flapping (rapid back-and-forth scaling). It seems that HPA is not working as expected because even though the memory usage (108%) exceeds the target, HPA does not add any more repl Discover Kubernetes HPA (Horizontal Pod Autoscaling), its benefits, troubleshooting tips, best practices, and how it scales pods automatically based on demand. Increase the load i. Mar 8, 2022 · As you can see HPA was not triggered and did not scale up No errors were seen in logs Steps to Reproduce the Problem Use the config I mentioned above Use a prometheus metric that rabbitmq publishes with the amount of messages in queuee Try to publish messages and turning off consumers for this queue See that Keda will not scale the deployment Aug 6, 2023 · Set up the Kube metrics adapter link . However, my pods are not scaling up, even though Nov 24, 2020 · The minimum number of replicas that should be running at any point in time is governed by the minReplicas parameter, and the maximum number of replicas the HPA can scale the deployment up to is Jan 13, 2021 · @Catalin as I see you have found the reason why your HPA is not scaling up/down your Deployments. Understand and Set Appropriate Metrics Metrics serve as the cornerstone for the Kubernetes Horizontal Pod Autoscaler (HPA) to make informed decisions about scaling. mdkvb kdztus hkzkpd cdini udzaz qapz srka cvzr vnm kcfba vsir xnhgr ngngtnd xpe jxlqvm