From 0ea82eb9e3ea4e418fcc7542f446e6e7231a41e0 Mon Sep 17 00:00:00 2001 From: cyrilico <19289022+cyrilico@users.noreply.github.com> Date: Thu, 25 Jul 2024 10:32:05 +0100 Subject: [PATCH] further clarify when to use new field Signed-off-by: cyrilico <19289022+cyrilico@users.noreply.github.com> --- docs/features/traffic-management/nginx.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/features/traffic-management/nginx.md b/docs/features/traffic-management/nginx.md index 8666085466..220ad7fd84 100644 --- a/docs/features/traffic-management/nginx.md +++ b/docs/features/traffic-management/nginx.md @@ -8,6 +8,7 @@ The Rollout controller will always set the following two annotations on the cana - `canary-weight: ` to indicate what percentage of traffic to send to the canary. If all traffic is routed to the stable Service, this is set to `0` You can provide additional annotations to add to the canary Ingress via the `additionalIngressAnnotations` or `canaryIngressAnnotations` field to enable features like routing by header or cookie. +While the former offers the possibility of reusing a common, injectable nginx annotation prefix, the latter allows defining custom full annotations of any group, which may be relevant for other, independent mechanisms, such as a third-party metrics scraper or some other infrastructure integration. ## Integration with Argo Rollouts