Skip to content

Commit

Permalink
further clarify when to use new field
Browse files Browse the repository at this point in the history
Signed-off-by: cyrilico <19289022+cyrilico@users.noreply.github.com>
  • Loading branch information
cyrilico committed Jul 25, 2024
1 parent ee3089b commit 0ea82eb
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/features/traffic-management/nginx.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ The Rollout controller will always set the following two annotations on the cana
- `canary-weight: <num>` 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
Expand Down

0 comments on commit 0ea82eb

Please sign in to comment.