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

Reach out to External Teams to Verify Operators on Multi-Arch Compute clusters

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • External Operator Verificiation for Multi-Arch
    • False
    • None
    • False
    • Not Selected
    • NEW
    • To Do
    • x86_64, ppc64le, s390x, aarch64
    • NEW

      Epic Goal

      • The goal of this epic is to identify 3rd party operators like CrowdStrike or the Cloudpak operators and to work with our contacts to let them know about the multi-arch compute feature and to encourage them to increase their testing to include coverage to validate these kinds of scenarios.

      Why is this important?

      • This is important because 3rd party and community operators are a core part of the value proposition for multi-arch, so extending connections to teams that own community operators is critical to ensuring that multi-arch compute based topologies are just as robust as homogeneous clusters.
      • Specific operators we'd like to see covered by this effort are:
        • ibm-cp-security-operator
        • falcon-operator
        • ibm-security-edr-operator
        • ibm-security-verify-operator
        • ibm-secuirty-verifiy-directory-operator
        • portworx
        • volsync-product
        • redis
        • postgres
        • IBM storage-scale / Fusion
        • ibm-cpd-scheduling-operator
        • ibm-common-service
        • ibm license
        • ibm-apiconnect

      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
            jpoulin Jeremy Poulin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: