clarify canary ingress

kubernetes · Nov 28, 2018 · 13e7e6a · 13e7e6a
1 parent 7b79341
commit 13e7e6a
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/docs/user-guide/nginx-configuration/annotations.md b/docs/user-guide/nginx-configuration/annotations.md
@@ -114,6 +114,8 @@ In some cases, you may want to "canary" a new set of changes by sending a small
 Canary rules are evaluated in order of precedence. Precedence is as follows: 
 `canary-by-header -> canary-by-cookie -> canary-weight` 
 
+**Note** that when you mark an ingress as canary, then all the other non-canary annotations will be ignored (inherited from the corresponding main ingress) except `nginx.ingress.kubernetes.io/load-balance` and `nginx.ingress.kubernetes.io/upstream-hash-by`.
+
 **Known Limitations**
 
 Currently a maximum of one canary ingress can be applied per Ingress rule.