XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • rhos-18.0.10 FR 3
    • rhos-18.0 FR 2 (Mar 2025)
    • watcher-operator
    • None
    • Add topology support to Watcher
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Proposed
    • Proposed
    • Done
    • watcher-operator-bundle-container-1.0.12-1
    • Proposed
    • rhos-workloads-evolution
    • Committed
    • 0% To Do, 0% In Progress, 100% Done

      Goal:

      Add ability to use TopologySpreadConstraints and Affinity / Anti-Affinity to schedule the pods on specific nodes.

       

      Acceptance Criteria:

      • Functional tests are created (as in https://github.com/openstack-k8s-operators/keystone-operator/blob/main/tests/functional/keystoneapi_controller_test.go#L1558 )
      • Kuttl tests to validate  topologySpreadConstraints are applied to the statefulset.
      • In crc-based jobs we can not test the actual behavior of the topology as it requires more that one master node to distribution of pods. However, in one of the existing jobs we can add a topology CR and add it as parameter to the Watcher CR. With that, at least we will know that the CR is properly handled.
      • The storage team has been working in creating a DT for it. At some point, it would be good to have a DT to validate all the services.

       

              amoralej1@redhat.com Alfredo Moralejo Alonso
              amoralej1@redhat.com Alfredo Moralejo Alonso
              David Sanz Moreno David Sanz Moreno
              rhos-workloads-evolution
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: