From ed8f0da4f9f31b689a44fcf8aaafbe4a54ada881 Mon Sep 17 00:00:00 2001 From: shivkumar dudhani Date: Thu, 10 Oct 2019 12:50:17 -0700 Subject: [PATCH] update documentation --- samples/README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/samples/README.md b/samples/README.md index 515c3a092d..c05f986c98 100644 --- a/samples/README.md +++ b/samples/README.md @@ -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.