From ffaeca51c5bcfd20cd9432080371defa4eb47552 Mon Sep 17 00:00:00 2001 From: Brian Grant Date: Fri, 7 Apr 2017 13:03:46 -0700 Subject: Clarify ownership of pod execution policy --- contributors/design-proposals/architecture.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/contributors/design-proposals/architecture.md b/contributors/design-proposals/architecture.md index 02516daa..3dac164e 100644 --- a/contributors/design-proposals/architecture.md +++ b/contributors/design-proposals/architecture.md @@ -202,6 +202,10 @@ concerns, and migration from physical/virtual machines. The Pod primitive is key [primary benefits](https://kubernetes.io/docs/whatisk8s/#why-containers) of deployment on modern cloud platforms, such as Kubernetes. +API admission control may reject pods or add additional scheduling constraints to them, but +Kubelet is the final arbiter of what pods can and cannot run on a given node, not the schedulers +or DaemonSets. + Kubelet also currently links in the [cAdvisor](https://github.com/google/cadvisor) resource monitoring agent. -- cgit v1.2.3