Help Center/ Cloud Container Instance/ User Guide/ Bursting to CCI/ CCE Cloud Bursting Engine for CCI/ FAQ

Updated on 2024-05-23 GMT+08:00

View PDF

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.

Parent topic: CCE Cloud Bursting Engine for CCI

Previous topic: Auto Scaling

Next topic: Security Vulnerability Responses

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.