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

Configurable fallbackArchitecture

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Multiarch-Tuning-Operator
    • None
    • Configurable fallbackArchitecture
    • None
    • 100% To Do, 0% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • Hide

      [2025/05/07] <DEFERRED> This epic is about a feature not prioritized at program/product level and requested by the DPTP team. The engineering team considers DPTP as a very valuable and early adopter of the operator, and they have given availability us to develop this feature on their own, according to their priorities and with our support. We are still available to take it if the DPTP team doesn't have resources to spend on this effort, as we think there is business value in having a fallback architecture set at configuration time for the MTO. However, we still need to prioritize it with product management.

      Show
      [2025/05/07] <DEFERRED> This epic is about a feature not prioritized at program/product level and requested by the DPTP team. The engineering team considers DPTP as a very valuable and early adopter of the operator, and they have given availability us to develop this feature on their own, according to their priorities and with our support. We are still available to take it if the DPTP team doesn't have resources to spend on this effort, as we think there is business value in having a fallback architecture set at configuration time for the MTO. However, we still need to prioritize it with product management.
    • None
    • None

      Epic Goal

      • To add a field, `fallbackArchitecture` in the ClusterPodPlacementConfig API, that is used by the podPlacementController when errors due to external dependencies occur (e.g., unavailability of the image registry).

      Why is this important?

      • Customers want to be able setting a fallback architecture to force the pods land into it when the MTO PodPlacementController is unable to inspect the images and compute the strong predicates for scheduling.

      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'.

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

                Created:
                Updated: