Help Center/ Ubiquitous Cloud Native Service/ FAQs/ Fleets/ What Can I Do If an Nginx Ingress Is in the Unready State After Being Deployed?

Updated on 2024-09-11 GMT+08:00

View PDF

What Can I Do If an Nginx Ingress Is in the Unready State After Being Deployed?

Context

The Nginx Ingress is in the unready state after being deployed.

Solution

Before creating an Nginx Ingress, install the Nginx Ingress Controller add-on for the corresponding cluster. If the add-on is not installed, the Nginx Ingress is in the unready state.

For details about how to install the add-on for the CCE cluster, see Creating Nginx Ingresses on the Console.
For details about how to install the add-on for the on-premises cluster, see Ingress-NGINX for Load Balancing at Layer 7.
For details about how to install add-ons for other types of clusters, see Nginx Ingress Controller.

Parent topic: Fleets

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.

Chatbot