Bug 1465375 - [RFE] Per project default pod affinity
Summary: [RFE] Per project default pod affinity
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Eric Paris
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-27 10:24 UTC by Javier Ramirez
Modified: 2021-09-09 12:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-11 21:17:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.