Help Center/ Cloud Container Instance (CCI)_Cloud Container Instance 1.0 (CCI 1.0)/ Best Practices/ Workload Management/ Disabling the Feature of Marking the virtual-kubelet Node as Unschedulable After CCI Pods Remain Pending for a Long Time
Updated on 2026-09-22 GMT+08:00
View PDF
Share

Disabling the Feature of Marking the virtual-kubelet Node as Unschedulable After CCI Pods Remain Pending for a Long Time

Procedure

  1. Install the CCE Cloud Bursting Engine for CCI add-on. For details, see Installing the Add-on.
  2. Select a CCE cluster node and use kubectl to view the Deployments of cceaddon-virtual-kubelet-virtual-kubelet and cceaddon-virtual-kubelet-resource-syncer. 

    kubectl get deploy -n kube-system | grep cceaddon-virtual-kubelet

  3. Modify the Deployments of cceaddon-virtual-kubelet-virtual-kubelet and cceaddon-virtual-kubelet-resource-syncer (to disable the resource stress testing).

    • Modify the Deployment of cceaddon-virtual-kubelet-resource-syncer. 
      kubectl edit deploy -n kube-system cceaddon-virtual-kubelet-resource-syncer

      Change CHECK_RESOURCE_PRESSURE to false, save the modification, and restart the pods.

    • Modify the Deployment of cceaddon-virtual-kubelet-virtual-kubelet. 
      kubectl edit deploy -n kube-system cceaddon-virtual-kubelet-virtual-kubelet

      Change CHECK_RESOURCE_PRESSURE to false, save the modification, and restart the pods.

  4. Ensure that the components are restarted. 

    kubectl get pod -n kube-system | grep cceaddon-virtual-kubelet

    Ensure that all cceaddon-virtual-kubelet-virtual-kubelet and cceaddon-virtual-kubelet-resource-syncer pods are in the Running state. Now the feature that marks the virtual-kubelet node as unschedulable after CCI pods are pending for a long time will be disabled.

Parent topic: Workload Management