Help Center>
Cloud Container Engine>
FAQs>
Networking>
Network Configuration>
Why Is the Backend Server Group of an ELB Automatically Deleted After a Service Is Published to the ELB?
Updated on 2024-07-04 GMT+08:00
Why Is the Backend Server Group of an ELB Automatically Deleted After a Service Is Published to the ELB?
Symptom
After a Service is published to ELB, the workload is normal, but the pod port of the Service is not published in time. As a result, the backend server group of the ELB is automatically deleted.
Answer
- If the ELB monitoring check fails during ELB creation, the backend server group will be deleted and will not be added after the Service becomes normal. If an existing SVC is updated, the backend server group is not deleted.
- When a node is added or deleted, the node access mode in the cluster may change due to the cluster status change. To ensure normal service running, the ELB performs a refresh operation. The process is similar to that of updating the ELB.
Suggestions
Optimize the application to speed up the startup.
Network Configuration FAQs
- How Does CCE Communicate with Other Huawei Cloud Services over an Intranet?
- How Do I Set the Port When Configuring the Workload Access Mode on CCE?
- How Can I Achieve Compatibility Between Ingress's property and Kubernetes client-go?
- How Do I Obtain the Actual Source IP Address of a Client After a Service Is Added into Istio?
- Why Cannot an Ingress Be Created After the Namespace Is Changed?
- Why Is the Backend Server Group of an ELB Automatically Deleted After a Service Is Published to the ELB?
- How Can Container IP Addresses Survive a Container Restart?
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
