What Can I Do If I Fail to Access a Service Through MCI?

If you fail to access a service after creating an MCI, check whether the MCI object is successfully configured.

Log in to the ELB console, locate the ELB instance based on the ID of the ELB instance bound to the MCI, and click the name of the ELB instance to access its details page. On the Listeners tab, locate the target listener and click Add/Edit Forwarding Policy. On the displayed page, click the name of the target backend server group to access the details page. Then, click the Backend Servers tab and check whether this ELB instance is successfully bound to the target workload.

1. If the backend server has been deleted, check whether the CIDR block of the pod conflicts with the VPC CIDR block of the ELB.

2. If there is no backend server in the backend server group, run the following command to query the corresponding event and rectify the fault based on the event information. Replace {MCIname} with the MCI name.

   kubectl describe mci {MCIname}

   If the following error information is displayed, check whether the listener port of the ELB instance is occupied:

   

   If the following error information is displayed, check whether the service name exists in the MCI:

   

   If the following error information is displayed, check whether the service port configured in the MCI is correct: