A canary Ingress has been configured, but traffic is not distributed according to the canary Ingress, or normal Ingress traffic is routed to the canary Service.

Cause analysis

In the Nginx Ingress Controller, canary rules are not applied to a single Ingress, but to all Ingresses that use the same Service. For details, see An Ingress with canary will impact all Ingresses with the same Service.

Solution

For Ingresses that need to enable canary support (including those using service-match and canary-* related annotations), create independent Services (including both production and canary Services) and point them to the original Pods, and then enable canary support for the corresponding Ingress.

Last updated: 2026.07.23 14:31:45

Public security network record in Beijing: No. 11010802032137