Frequently asked questions about MSE Ingress gateways, including supported versions, Ingress class precedence, traffic rule management, and troubleshooting.
Which Ingress versions does the MSE cloud-native gateway support?
MSE cloud-native gateways support Ingresses of the networking.k8s.io/v1beta1 or networking.k8s.io/v1 version. You can associate a cloud-native gateway with an ACK cluster running Kubernetes V1.18.0 or later.
Which Ingress class takes effect when both annotation and spec field are set?
Cloud-native gateways follow the Kubernetes Ingress standard: the kubernetes.io/ingress.class annotation takes precedence over Ingress Spec.IngressClassName.
Can I mix manual and automatic Ingress traffic rule management?
Yes. You can use both approaches together:
-
Manual management (MSE console): Define Ingress traffic rules directly in the MSE console. This is the recommended approach when you need explicit control over domain and route configurations.
-
Automatic management (ACK console): Define Ingress resources in the ACK console. The gateway monitors changes and applies configurations in real time.
Manually managed rules (MSE console) take priority over automatically managed rules (Ingress resources). If a manually defined rule and an Ingress-derived rule target the same domain or route, the manually managed rule takes effect.
When you use both approaches, domain name and route configurations derived from Ingress resources cannot be edited in the MSE console. Their lifecycle is managed by the Ingress resources in the ACK console.
Why does the console show a domain name or route as "Unavailable"?
Log in to the MSE console. On the Routes page, click the Routes or Domain Names tab, then hover over Unavailable to see the specific cause.