Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-10294

Configurable Affinity/TopologySpreadConstraints to control pod AZ placement

XMLWordPrintable

    • Configurable TopologySpreadConstraints to control pod AZ placement
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Proposed
    • No Docs Impact
    • Done
    • RHOSSTRAT-77 - Support Distributed ctlplane nodes across low latency L3 interconnected DataCenters
    • openstack-operator-bundle-container-1.0.7-9
    • Proposed
    • Proposed
    • Release Note Not Required
    • Regression Only

      Basic affinity rules are currently used to spread pods across different hosts.
      For high-availablility control plane deployments across multiple availability zones we will need to spread pods based on an arbitrary node label e.g topology.kubernetes.io/zone.

      The affinity rules should also be strict (currently permissive) for HA stateful services to ensure 2 pods cannot be placed on the same failure domain.

              rhn-engineering-owalsh Oliver Walsh
              rhn-engineering-owalsh Oliver Walsh
              Francesco Pantano
              rhos-dfg-ospk8s
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: