All Products
Search
Document Center

Container Compute Service:Ingress diagnostics

Last Updated:Mar 26, 2026

Alibaba Cloud Container Compute Service (ACS) provides Ingress diagnostics to help you identify and fix common Ingress issues. This topic describes what each diagnostic item checks and how to resolve failures.

The diagnostics feature covers four categories: Ingress, startup parameters, Ingress pod error log, and Ingress controller Server Load Balancer (SLB) instance.

Important

When you run a diagnostic, ACS runs a data collection program on each node in the cluster. The program collects the system version, load metrics, container component status, and key error messages from system logs. ACS does not collect business data or sensitive information.

Ingress diagnostic items

Note

Diagnostic items may vary based on your cluster configuration. The actual items shown on the diagnostic page take precedence.

Ingress

Diagnostic item

Description

How to fix

Ingress check

Checks whether the specified Ingress exists.

Verify that an Ingress rule is created for the URL. If the URL is valid, review the Ingress rules — for example, check whether a regular expression is used as the path or whether the use-regex annotation is set.

Ingress name

Displays the names of matching Ingress rules.

No action required.

Ingress IP address check

Checks whether the Ingress controller has allocated an IP address to the Ingress.

If no IP address is allocated, verify that the Ingress controller is referenced in the IngressClass of the Ingress and that the Ingress controller is running as expected. Fix the issue based on the diagnostic result.

base-url-scheme check

Checks whether the nginx.ingress.kubernetes.io/base-url-scheme annotation is present. This annotation was deprecated in Ingress controller 0.22.0.

Check the Ingress controller version, then remove the annotation or replace it with a supported alternative. For available annotations, see the NGINX Ingress Controller annotation reference.

grpc-backend check

Checks whether the nginx.ingress.kubernetes.io/grpc-backend annotation is present. This annotation was deprecated in Ingress controller 0.21.0.

Check the Ingress controller version, then remove the annotation or replace it with a supported alternative. For available annotations, see the NGINX Ingress Controller annotation reference.

mirror-uri check

Checks whether the nginx.ingress.kubernetes.io/mirror-uri annotation is present. This annotation was deprecated in Ingress controller 0.24.0.

Check the Ingress controller version, then remove the annotation or replace it with a supported alternative. For available annotations, see the NGINX Ingress Controller annotation reference.

secure-backends check

Checks whether the nginx.ingress.kubernetes.io/secure-backends annotation is present. This annotation was deprecated in Ingress controller 0.21.0.

Check the Ingress controller version, then remove the annotation or replace it with a supported alternative. For available annotations, see the NGINX Ingress Controller annotation reference.

session-cookie-hash check

Checks whether the nginx.ingress.kubernetes.io/session-cookie-hash annotation is present. This annotation was deprecated in Ingress controller 0.24.0.

Check the Ingress controller version, then remove the annotation or replace it with a supported alternative. For available annotations, see the NGINX Ingress Controller annotation reference.

nginx.com/nginx.org check

Checks whether the Ingress uses annotations prefixed with nginx.com or nginx.org. These annotations are only compatible with the commercial NGINX Ingress controller and are not supported by the open source version.

Replace these annotations with the equivalent open source NGINX Ingress controller annotations. For details, see NGINX Ingress management or the NGINX Ingress Controller documentation.

Status of Canary

Checks whether nginx.ingress.kubernetes.io/canary: "true" is set. Without this annotation, the Canary feature does not take effect, even if other Canary annotations are present.

Add nginx.ingress.kubernetes.io/canary: "true" to the Ingress rules.