Loading
search-img
Title
Pods can't be scheduled because autoscaling is disabled

You may see a warning message similar to the following stating that autoscaling is disabled for a pod after Flexera attempts to scale up an instance at least 5 times. 

WARN, Pod Metrics-Server-xxxxx Has Failed To Schedule For 76 Minutes. Autoscaling Disabled For Pod Metrics-Server-xxxxx
WARN, Pod Redis-0 Has Failed To Schedule For 76 Minutes. Autoscaling Disabled For Pod Redis-0
WARN, Pod Kube-Dns-Autoscaler-xxxxx Has Failed To Schedule For 76 Minutes. Autoscaling Disabled For Pod Kube-Dns-Autoscaler-xxxxx
WARN, Pod Worker-Deployment-xxxxx Has Failed To Schedule For 76 Minutes. Autoscaling Disabled For Pod Worker-Deployment-xxxxx
WARN, Pod Kube-Dns-xxxxx Has Failed To Schedule For 76 Minutes. Autoscaling Disabled For Pod Kube-Dns-xxxxx

This usually happens when the autoscaler launches new nodes, but Kubernetes still can’t schedule the pod. Flexera disables autoscaling for that pod to avoid an endless scaling loop. These checks help you identify why the pod can’t schedule and how to fix the issue.

Solution

  1. Confirm that new nodes register with the cluster
    Flexera may launch instances for a pending pod, but the nodes won’t be usable until they fully register with Kubernetes. If registration fails, no node is available to schedule the pod. Check your node initialization, bootstrap process, and any conditions that may prevent nodes from joining the cluster.

  2. If you use the AWS EBS CSI driver, check the ebs‑csi‑node DaemonSet
    Make sure the DaemonSet pods for the EBS CSI node component run on every node. If the DaemonSet has issues or if virtual node groups include taints that block DaemonSet scheduling, the storage driver won’t run on the node. If a pending pod uses a persistent volume claim that relies on this driver, the pod won’t schedule until the DaemonSet runs.

  3. If you use GPU nodes, confirm that GPU resources are exposed
    Kubernetes exposes GPU resources only when the Nvidia device plugin DaemonSet runs on each GPU node. If the DaemonSet isn’t running or is blocked by taints, the node won’t report GPU capacity. If a pod requests GPU resources, Flexera launches a GPU instance, but Kubernetes won’t schedule the pod until the node exposes its GPU resources.

    To learn more, see the Nvidia device plugin documentation here. 

Outcome
After you resolve node registration, DaemonSet issues, or GPU plugin problems, Kubernetes should schedule the pod and Flexera autoscaling should re‑enable for that workload.
Was this helpful?
Support Hub
Create a case with Support
0/255
Upload Attachment
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to cancel the case creation?

Are you sure you want to close this case

Get Hotline support
Products Region Phone Numbers
FlexNet Operations
FlexNet Embedded
FlexNet Publisher
FlexNet Connect
FlexNet Code Insight
InstallAnywhere
InstallShield 		North America  * +1 630-332-2513 (toll)
+1 877-279-2853 (toll-free in North America)
Europe  * +44 1925 944367 (toll)
+44 800 047 8642 (toll-free in Europe)
Japan  * +81 3-4540-5335 (select option 2)
Australia  * +61 3 9895 2177
+61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics)
Compliance Intelligence 		Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.
Book an Appointment
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Revenera Assistant

Revenera Assistant
+1.800.374.4353
CONTACT US REVENERA.COM FLEXERA.com
© 2026 Flexera Software. All Rights Reserved.
Privacy policy Terms and conditions Flexera Community Contact Us
Loading
Pods can't be scheduled because autoscaling is disabled