mirror of https://github.com/k3s-io/k3s
649c0ddd0e
Automatic merge from submit-queue [AppArmor] Hold bad AppArmor pods in pending rather than rejecting Fixes https://github.com/kubernetes/kubernetes/issues/32837 Overview of the fix: If the Kubelet needs to reject a Pod for a reason that the control plane doesn't understand (e.g. which AppArmor profiles are installed on the node), then it might contiinuously try to run the pod on the same rejecting node. This change adds a concept of "soft rejection", in which the Pod is admitted, but not allowed to run (and therefore held in a pending state). This prevents the pod from being retried on other nodes, but also prevents the high churn. This is consistent with how other missing local resources (e.g. volumes) is handled. A side effect of the change is that Pods which are not initially runnable will be retried. This is desired behavior since it avoids a race condition when a new node is brought up but the AppArmor profiles have not yet been loaded on it. ``` release-note Pods with invalid AppArmor configurations will be held in a Pending state, rather than rejected (failed). Check the pod status message to find out why it is not running. ``` @kubernetes/sig-node @timothysc @rrati @davidopp |
||
|---|---|---|
| .. | ||
| BUILD | ||
| doc.go | ||
| fake_handler_runner.go | ||
| handlers.go | ||
| handlers_test.go | ||
| interfaces.go | ||
| predicate.go | ||