From 7de8cda84c294f8cd7ad12655f16cee49404973d Mon Sep 17 00:00:00 2001 From: jianglingxia Date: Wed, 26 Apr 2017 14:37:11 +0800 Subject: [PATCH] jlx426 --- .../debug-pod-replication-controller.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md b/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md index e3269cfb67..99c30df9d1 100644 --- a/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md +++ b/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md @@ -38,7 +38,7 @@ case you can try several things: to make room for pending pods. * Check that the pod is not larger than your nodes. For example, if all - nodes have a capacity of `cpu:1`, then a pod with a limit of `cpu: 1.1` + nodes have a capacity of `cpu:1`, then a pod with a request of `cpu: 1.1` will never be scheduled. You can check node capacities with the `kubectl get nodes -o `