Skip to content

Commit 4f724c5

Browse files
authored
Merge pull request #275417 from dem108/patch-29
Make the section for in-place rolling update more visible
2 parents b792665 + e6509ac commit 4f724c5

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/machine-learning/how-to-deploy-online-endpoints.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1215,12 +1215,11 @@ There currently isn't an option to update the deployment using an ARM template.
12151215

12161216
---
12171217

1218-
1219-
The update to the deployment in this section is an example of an in-place rolling update.
1220-
1221-
* For a managed online endpoint, the deployment is updated to the new configuration with 20% nodes at a time. That is, if the deployment has 10 nodes, 2 nodes at a time are updated.
1222-
* For a Kubernetes online endpoint, the system iteratively creates a new deployment instance with the new configuration and deletes the old one.
1223-
* For production usage, you should consider [blue-green deployment](how-to-safely-rollout-online-endpoints.md), which offers a safer alternative for updating a web service.
1218+
> [!NOTE]
1219+
> The update to the deployment in this section is an example of an in-place rolling update.
1220+
> * For a managed online endpoint, the deployment is updated to the new configuration with 20% nodes at a time. That is, if the deployment has 10 nodes, 2 nodes at a time are updated.
1221+
> * For a Kubernetes online endpoint, the system iteratively creates a new deployment instance with the new configuration and deletes the old one.
1222+
> * For production usage, you should consider [blue-green deployment](how-to-safely-rollout-online-endpoints.md), which offers a safer alternative for updating a web service.
12241223

12251224
### (Optional) Configure autoscaling
12261225

0 commit comments

Comments
 (0)