Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2472

Predictable latest MCE HO build locations

XMLWordPrintable

    • Quality / Stability / Reliability
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • 7
    • None
    • None
    • None
    • None
    • None

      Feature Overview (aka. Goal Summary)  

      Have an easy way for quality engineering to find the latest build of the HyperShift Operator for self-managed hosted control planes.

      Goals (aka. expected user outcomes)

      There is a non-ambiguous place to find the latest image built by Konflux for each MCE release

      Requirements (aka. Acceptance Criteria):

      • Builds are discoverable
      • There is a tag that points to the latest build
      • The builds are the same that might eventually be selected for a .0 or a .z release.

       

      Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

      Deployment considerations List applicable specific needs (N/A = not applicable)
      Self-managed, managed, or both self-managed
      Classic (standalone cluster) No
      Hosted control planes Yes
      Multi node, Compact (three node), or Single node (SNO), or all All supported configurations
      Connected / Restricted Network All supported configurations
      Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) All supported configurations
      Operator compatibility All supported configurations
      Backport needed (list applicable versions) All supported MCE releases
      UI need (e.g. OpenShift Console, dynamic plugin, OCM) n/a
      Other (please specify)  

      Use Cases (Optional):

      Verification of self-managed features and bugs

      Background

      Currently QE sometimes end up making their own builds for verification, which is costly and might not fully match what ends up getting delivered.

      Documentation Considerations

      No documentation necessary for downstream.

              asegurap1@redhat.com Antoni Segura Puimedon
              asegurap1@redhat.com Antoni Segura Puimedon
              None
              None
              Liangquan Li Liangquan Li
              Liangquan Li Liangquan Li
              Liangquan Li Liangquan Li
              Senthamilarasu S Senthamilarasu S
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: