Help Center/ Cloud Container Engine/ FAQs/ Networking/ Network Configuration/ Why Cannot an Ingress Be Created After the Namespace Is Changed?
Updated on 2024-07-04 GMT+08:00

Why Cannot an Ingress Be Created After the Namespace Is Changed?

Symptom

An ingress can be created in the default namespace, but cannot be created in other namespaces.

Cause Analysis

After a load balancer is created, an HTTP listener is created in the default namespace for port 80. In CCE, only ingresses of the same port can be created in the same namespace (the actual forwarding policies can be distinguished based on domain names and Services). Therefore, ingresses of the same port cannot be created in other namespaces (a port conflict message is displayed).

Solution

You can use YAML files to create ingresses. Port conflicts occur when you create ingresses on the CCE console, but not when you do so in the backend.