Skip to content

Commit

Permalink
Docs change
Browse files Browse the repository at this point in the history
Signed-off-by: zachaller <[email protected]>
  • Loading branch information
zachaller committed Jun 16, 2022
1 parent ff87eda commit 9c8b5fd
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion docs/features/traffic-management/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,12 @@ When traffic routing is enabled, you have the ability to also let argo rollouts
controlling the traffic weight to the canary. Two such routing rules are header and mirror based routes. When using these
routes we also have to set a route precedence with the upstream traffic router. We do this using the `spec.strategy.canary.trafficRouting.managedRoutes`
field which is an array the order of the items in the array determine the precedence. This set of routes will also be placed
in the order specified on top of any other routes defined manually. Here is an example:
in the order specified on top of any other routes defined manually.

#### WARNING: All routes listed in managed routes will be removed at the end of a rollout or on an abort. Do not put any manually created routes in the list.


Here is an example:

```yaml
apiVersion: argoproj.io/v1alpha1
Expand Down

0 comments on commit 9c8b5fd

Please sign in to comment.