Merge pull request kyverno#1329 from hubwoop/main

adds cpu limit to pod requests limits example
realshuting · Dec 1, 2020 · 1c73dd9 · 1c73dd9
2 parents 370828a + c3d204a
commit 1c73dd9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/samples/RequirePodRequestsLimits.md b/samples/RequirePodRequestsLimits.md
@@ -1,6 +1,6 @@
 # Require pod resource requests and limits
 
-Application workloads share cluster resources. Hence, it is important to manage resources assigned to each pod.  It is recommended that `resources.requests` and `resources.limits` are configured per pod and include CPU and memory resources. Other resources such as GPUs may also be specified as needed.
+Application workloads share cluster resources. Hence, it is important to manage resources assigned to each pod.  It is recommended that `resources.requests.cpu`, `resources.requests.memory` and `resources.limits.memory` are configured per pod. Other resources such as GPUs may also be specified as needed.
 
 If a namespace level request or limit is specified, defaults will automatically be applied to each pod based on the `LimitRange` configuration.
 

diff --git a/samples/best_practices/require_pod_requests_limits.yaml b/samples/best_practices/require_pod_requests_limits.yaml
@@ -6,7 +6,7 @@ metadata:
     policies.kyverno.io/category: Workload Management
     policies.kyverno.io/description: As application workloads share cluster resources, it is important 
       to limit resources requested and consumed by each pod. It is recommended to require 
-      'resources.requests' and 'resources.limits' per pod. If a namespace level request or limit is 
+      'resources.requests' and 'resources.limits.memory' per pod. If a namespace level request or limit is 
       specified, defaults will automatically be applied to each pod based on the 'LimitRange' configuration.
 spec:
   validationFailureAction: audit