From 704e14a2d79b501c7944f860f25217b43b0ae606 Mon Sep 17 00:00:00 2001 From: WanLinghao Date: Tue, 1 Aug 2017 16:49:23 +0800 Subject: [PATCH] Update assign-pod-node.md (#4356) * Update assign-pod-node.md I am a freshman on Kubernetes development.When I use the affinity feature,it confuses me that why the pod won't stop after I changing the node's label which makes the node no longer satisfy the affinity condition.Although I learn how this feature works by community, I hope the documentation can help people especially fresh man better.^_^ * Update assign-pod-node.md after review I have fixed the commit after review --- docs/concepts/configuration/assign-pod-node.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index eef8ca1908..d2a379f6ee 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -139,6 +139,8 @@ If you specify multiple `nodeSelectorTerms` associated with `nodeAffinity` types If you specify multiple `matchExpressions` associated with `nodeSelectorTerms`, then the pod can be scheduled onto a node **only if all** `matchExpressions` can be satisfied. +If you remove or change the label of the node where the pod is scheduled, the pod won't be removed. In other words, the affinity selection works only at the time of scheduling the pod. + For more information on node affinity, see the design doc [here](https://git.k8s.io/community/contributors/design-proposals/nodeaffinity.md).