Merge pull request #36060 from resouer/fix-service-affinity

Automatic merge from submit-queue Add use case to service affinity Also part of nits in refactoring predicates, I found the explanation of `serviceaffinity` in its comment is very hard to understand. So I added example instead here to help user/developer to digest it.

Merge pull request #36060 from resouer/fix-service-affinity
59ad9a30 · Kubernetes Submit Queue · GitHub · d9aed2c5 · a0e836a3 · 59ad9a30
Commit 59ad9a30 authored Dec 15, 2016 by Kubernetes Submit Queue Committed by GitHub Dec 15, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 5 additions and 0 deletions

predicates.go plugin/pkg/scheduler/algorithm/predicates/predicates.go +5 -0

No files found.
--- a/plugin/pkg/scheduler/algorithm/predicates/predicates.go
+++ b/plugin/pkg/scheduler/algorithm/predicates/predicates.go
@@ -737,6 +737,11 @@ func NewServiceAffinityPredicate(podLister algorithm.PodLister, serviceLister al
 // the same service are running on nodes with
 // the exact same ServiceAffinity.label values).
 //
+// For example:
+// If the first pod of a service was scheduled to a node with label "region=foo",
+// all the other subsequent pods belong to the same service will be schedule on
+// nodes with the same "region=foo" label.
+//
 // Details:
 //
 // If (the svc affinity labels are not a subset of pod's label selectors )