Uploaded image for project: 'Multiple Architecture Enablement'
  1. Multiple Architecture Enablement
  2. MULTIARCH-4283 MMO QE enablement and test cases design/implementation
  3. MULTIARCH-4318

[E2E//PodPlacementOperand] Single vs Multi container images

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • None
    • False
    • None
    • False
    • NEW
    • OCPSTRAT-1289 - [Tech Preview] Multiarch Tuning Operator
    • x86_64, ppc64le, s390x, aarch64
    • Multi-Arch Sprint 250, Multi-Arch Sprint 251, Multi-Arch Sprint 252, Multi-Arch Sprint 253, Multi-Arch Sprint 254, Multi-Arch Sprint 255

      2) pods with one container (image single-arch)
      3) pods with one container (image multi-arch)
      4) pods with more containers: 1 single arch, the other multiarch
      5) pods with more containers, all multiarch images: for example one only amd64-arm64, the other arm64-ppc64le => epected affinity: only arm64

      We can use statefulset as higher-level object for the e2e.

      The integration tests already cover pods.

            lwan-wanglin Lin Wang
            rhn-support-adistefa Alessandro Di Stefano
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: