Skip to content

Commit ae9f5cf

Browse files
resolve comments.
1 parent fa0a721 commit ae9f5cf

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/machine-learning/how-to-deploy-azure-kubernetes-service.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ Azureml-fe scales both up (vertically) to use more cores, and out (horizontally)
8989

9090
When scaling down and in, CPU usage is used. If the CPU usage threshold is met, the front end will first be scaled down. If the CPU usage drops to the scale-in threshold, a scale-in operation happens. Scaling up and out will only occur if there are enough cluster resources available.
9191

92-
When scale-up or scale-down, azureml-fe pods will be restarted to apply the cpu/memory changes.
92+
When scale-up or scale-down, azureml-fe pods will be restarted to apply the cpu/memory changes. Inferencing requests are not affected by the restarts.
9393

9494
<a id="connectivity"></a>
9595

@@ -107,7 +107,7 @@ The following diagram shows the connectivity requirements for AKS inferencing. B
107107

108108
For general AKS connectivity requirements, see [Control egress traffic for cluster nodes in Azure Kubernetes Service](../aks/limit-egress-traffic.md).
109109

110-
For access azureml behind firewall, see [How to access azureml behind firewall](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/machine-learning/how-to-access-azureml-behind-firewall.md).
110+
For accessing Azure ML services behind a firewall, see [How to access azureml behind firewall](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/machine-learning/how-to-access-azureml-behind-firewall.md).
111111

112112
### Overall DNS resolution requirements
113113

0 commit comments

Comments
 (0)