Bug 1465375 - [RFE] Per project default pod affinity
[RFE] Per project default pod affinity
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE (Show other bugs)
3.6.0
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Eric Paris
Xiaoli Tian
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-27 06:24 EDT by Javier Ramirez
Modified: 2017-12-05 04:37 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Javier Ramirez 2017-06-27 06:24:09 EDT
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

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