On this page

Show all

Help Center/ Application Service Mesh/ FAQs/ Adding a Service/ What Do I Do If an Added Gateway Does Not Take Effect?

What Do I Do If an Added Gateway Does Not Take Effect?

Updated on 2023-07-03 GMT+08:00

View PDF

The possible cause is that the Gateway-related resource configurations are missing or incorrect. Do as follows to locate the fault:

Log in to the Elastic Load Balance console, check whether the external port and ECSs are successfully listened by the load balancer.
Log in to the cluster and run the kubectl get gateway -n istio-system command to check whether the IP address, domain name, and port number are configured for the Gateway. Run the kubectl get svc -n istio-system command to check whether the ingress Gateway has the corresponding IP address and port and is not in the pending status.
Check whether the internal access protocol of the service added to the service mesh is consistent with the external access protocol configured for the service's Gateway.
If the ERR_UNSAFE_PORT error is displayed when you use a browser to access the service, that is because the port is identified as a dangerous port by the browser. In this case, you need to use another external port.

Parent topic: Adding a Service

Thank you very much for your feedback. We will continue working to improve the documentation.

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