Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-6088

Provide affinity and anti-affinity for EgressIPs

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • SDN
    • None
    • False
    • None
    • False
    • Not Selected

      What is the nature and description of the request?

      We would like to be bale to specify Affinity and anti-affinity for EgressIPs, so we make sure that specific EgressIPs are not assigned on the same node.

      Why does the customer need this?

      The goal is to avoid service outages caused by overloaded network nodes, which was experienced several times in the past. EgressIPs of these large projects were assigned to the same node. As a result, the network node became 100% overloaded on CPU and gradually on RAM, leading to a partial outage of the affected high-throughput services and a partial outage of the lower-throughput services that had their EgressIP on the same network node as the larger projects.

      How would the customer like to achieve this?

      By introducing the same Affinity and Anti-affinity concept as for pods:

          Placing pods relative to other pods using affinity and anti-affinity rules

              mcurry@redhat.com Marc Curry
              rhn-support-rhodain1 Roman Hodain
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: