FAQ
Symptom 1: Pods cannot be scheduled to CCI. After running the kubectl get node command on the CCE cluster console, the virtual-kubelet node is in the SchedulingDisabled state.
Cause: CCI resources are sold out. As a result, scheduling to CCI failed, and the bursting node will be locked for half an hour, during which the resources cannot be scheduled to CCI.
Solution: Use kubectl to check the status of the bursting node on the CCE cluster console. If the bursting node is locked, you can manually unlock it.
Symptom 2: Elastic scheduling to CCI is unavailable.
Cause: The subnet where the CCE cluster resides overlaps with 10.247.0.0/16, which is the CIDR block reserved for the Service in the CCI namespace.
Solution: Reset a subnet for the CCE cluster.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot