Docs

Volcengine Kubernetes Engine

Add-on FAQs

How do I handle add-on scheduling failures?

How do I handle add-on scheduling failures?

Issue description

After you install an add-on in the VKE console, the add-on remains in the scheduling failed state, as shown in the following figure.

Cause analysis

In most cases, add-on scheduling failures are caused by the following four reasons:

No available nodes exist in the cluster.

Available nodes exist in the cluster, but they are in an abnormal status, or the CPU or memory of the nodes is insufficient.

Available nodes exist in the cluster. The nodes are in a normal status, and sufficient resources exist on the nodes. However, taints exist on the nodes that the add-on pods cannot tolerate.

Available nodes exist in the cluster. The nodes are in a normal status, and sufficient resources exist on the nodes. However, these nodes cannot satisfy the affinity scheduling requirements of the add-on pods.

Solution

Non-system managed add-ons: Troubleshoot the scheduling issue, uninstall the add-on, and then reinstall it based on the description in How do I fix a failure in scheduling a pod in the Pending state?

System-managed add-ons: You cannot independently resolve scheduling failures for this type of add-on. Contact the technical support of Volcano Engine, or submit a ticket to obtain technical support.

Add-ons with the identifier shown in the following figure are system-managed add-ons. You can also obtain the information about system-managed add-ons based on the description in Add-on overview.

Last updated: 2026.07.23 14:31:46