Bug 1465375

Summary: [RFE] Per project default pod affinity
Product: OpenShift Container Platform Reporter: Javier Ramirez <javier.ramirez>
Component: RFEAssignee: Eric Paris <eparis>
Status: CLOSED DEFERRED QA Contact: Xiaoli Tian <xtian>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: aos-bugs, jokerman, mmccomas, simon.gunzenreiner, sjenning
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-11 21:17:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Javier Ramirez 2017-06-27 10:24:09 UTC 
To optimize latency issues in a a set of collaborating pods within one project, we would like to request a "default" pod affinity configuration that a platform administrator can define per namespace (similar to the default node selector).

With this feature, we would be able to  bind a set of collaborating pods to a preferred Availability Zone (if a pod does not explicitly specify a pod affinity); this would be used to minimize cross site traffic, yes, with the price of reduced availability).

Related:
https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity
Comment 6 Rory Thrasher 2019-06-11 21:17:00 UTC 
Red Hat is moving OpenShift feature requests to a new JIRA RFE system. This bz (RFE) has been identified as a feature request which is still being evaluated and has been moved.

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.

https://.jira.coreos.com/browse/RFE-165