Skip to content

Commit ef8ade3

Browse files
authored
Update how-to-safely-rollout-managed-endpoints.md
Explain mirror traffic behavior when invoking while specifying deployment.
1 parent d12ca1f commit ef8ade3

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/machine-learning/how-to-safely-rollout-managed-endpoints.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,9 +121,13 @@ az ml online-endpoint update --name $ENDPOINT_NAME --mirror-traffic "green=10"
121121
> [!IMPORTANT]
122122
> Mirroring has the following limitations:
123123
> * You can only mirror traffic to one deployment.
124-
> * A deployment can only be set to live or mirror traffic, not both.
125124
> * Mirrored traffic is not currently supported with K8s.
126125
> * The maximum mirrored traffic you can configure is 50%. This limit is to reduce the impact on your endpoint bandwidth quota.
126+
>
127+
> Also note the following behavior:
128+
> * A deployment can only be set to live or mirror traffic, not both.
129+
> * You can send traffic directly to the mirror deployment by specifying the deployment set for mirror traffic.
130+
> * You can send traffic directly to the live deployment by specifying the deployment set for live traffic, but in this case the traffic won't be mirrored to the mirror deployment. Mirror traffic is routed from traffic sent to endpoint without specifying the deployment.
127131
128132
:::image type="content" source="./media/how-to-safely-rollout-managed-endpoints/endpoint-concept-mirror.png" alt-text="Diagram showing 10% traffic mirrored to one deployment.":::
129133

0 commit comments

Comments
 (0)