mirror of
https://github.com/kyverno/kyverno.git
synced 2025-03-31 03:45:17 +00:00
Merge pull request #1329 from hubwoop/main
adds cpu limit to pod requests limits example
This commit is contained in:
commit
1c73dd9107
2 changed files with 2 additions and 2 deletions
|
@ -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.
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Add table
Reference in a new issue