Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-5280

As a user I want to setup per-namespace weights for the architectures to be consumed by pods in a mixed cluster [phase1]

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Namespace Scoped PodPlacementConfig and reconciler
    • Future Sustainability
    • 50% To Do, 25% In Progress, 25% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      [2025/07/03] <YELLOW> Green for release

      • Development is in progress, but slightly at risk

      [2025/06/18] <GREEN> Green for release

      • Development is in progress and green

      [2025/06/11] <GREEN> Green for release

      • PRs are WIP in progress for the feature
      Show
      [2025/07/03] <YELLOW> Green for release Development is in progress, but slightly at risk [2025/06/18] <GREEN> Green for release Development is in progress and green [2025/06/11] <GREEN> Green for release PRs are WIP in progress for the feature
    • None
    • None

      Epic Goal

      • To implement a new, namespace-scoped, CR: PodPlacementConfig
      • The reconciler will take care of mutating the pod according to the configuration stored in the PodPlacementConfig

      Why is this important?

      • Users are willing to set different configurations for the preferred affinities related to the architecture in different namespaces for different workloads.

      Design document

      https://github.com/openshift/multiarch-tuning-operator/blob/main/docs/enhancements/MTO-0002-local-pod-placement.md

       

      Scenarios
      1. …

      Acceptance Criteria

      • (Enter a list of Acceptance Criteria unique to the Epic)

      Dependencies (internal and external)
      1. …

      Previous Work (Optional):
      1. …

      Open questions::
      1. …

      Done Checklist

      • CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
      • Release Enablement: <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
      • QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
      • QE - Automated tests merged: <link or reference to automated tests>
      • QE - QE to verify documentation when testing
      • DOC - Downstream documentation merged: <link to meaningful PR>
      • All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.

              rhn-support-adistefa Alessandro Di Stefano
              rhn-support-adistefa Alessandro Di Stefano
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: