mirrors/kyverno
mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2025-03-31 03:45:17 +00:00
Code Activity

update documentation

Browse source
This commit is contained in:
shivkumar dudhani 2019-10-10 12:50:17 -07:00
parent dbc35eb8f4
commit ed8f0da4f9
1 changed files with 2 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
samples/README.md
View file

@ -79,13 +79,12 @@ In order to limit the quantity of objects, as well as the total amount of comput
***Policy YAML***: [require_namespace_quota.yaml](best_practices/require_namespace_quota.yaml)
## Require resource quota
## Require pod resource requests and limits
When several users or teams share a cluster with a fixed number of nodes, there is a concern that one team could use more than its fair share of resources. To prevent a team taking up more than their fair share of the cluster, it is usually a best practice to configure resource quota for the application.
As workloads share the host cluster, it is essential to administer and limit resources requested and consumed by the pod. It is a good practice to always specify `resources.requests` and `resources.limits` per pod.
***Policy YAML***: [require_pod_requests_limits.yaml](best_practices/require_pod_requests_limits.yaml)
## Default health probe
Setting the health probe ensures an application is highly-avaiable and resilient. Health checks are a simple way to let the system know if an application is broken, and it helps the application quickly recover from failure.