Skip to content

Commit 0ffbdce

Browse files
authored
Update developer-best-practices-resource-management.md
Edited line 34 and line 50 for grammar, requires -> require
1 parent 3bcef8b commit 0ffbdce

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/aks/developer-best-practices-resource-management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Use pod requests and limits to manage compute resources within an AKS cluster. P
3131

3232
*Pod requests* define a set amount of CPU and memory the pod needs regularly.
3333

34-
In your pod specifications, it's important you define these requests and limits based on the above information. If you don't include these values, the Kubernetes scheduler can't consider the resources your applications requires to help with scheduling decisions.
34+
In your pod specifications, it's important you define these requests and limits based on the above information. If you don't include these values, the Kubernetes scheduler can't consider the resources your applications require to help with scheduling decisions.
3535

3636
Monitor the performance of your application to adjust pod requests. If you underestimate pod requests, your application may receive degraded performance due to over-scheduling a node. If requests are overestimated, your application may have increased scheduling difficulty.
3737

@@ -47,7 +47,7 @@ Monitor the performance of your application at different times during the day or
4747

4848
> [!IMPORTANT]
4949
>
50-
> In your pod specifications, define these requests and limits based on the above information. Failing to include these values prevents the Kubernetes scheduler from accounting for resources your applications requires to help with scheduling decisions.
50+
> In your pod specifications, define these requests and limits based on the above information. Failing to include these values prevents the Kubernetes scheduler from accounting for resources your applications require to help with scheduling decisions.
5151
5252
If the scheduler places a pod on a node with insufficient resources, application performance is degraded. Cluster administrators **must set *resource quotas*** on a namespace that requires you to set resource requests and limits. For more information, see [resource quotas on AKS clusters][resource-quotas].
5353

0 commit comments

Comments
 (0)