Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-8026

Provision long-lived dual-stack OCP cluster for downstream testing (Manually)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • OSSM 3.0.0
    • Istio, QE, Sail Operator

      As part of promoting dualStack to Tech Preview+ in the OSSM 3 release, we need a CI job to validate the integration tests with Istio deployed in dualStack mode (and optionally in IPv4 mode). From the Jira OSSM-3810, we know that the OpenShift team already has automation in place to create dualStack OCP clusters on the OSP 17.1 platform. Additionally, we have a Google Doc outlining the manual steps for developers who are interested in deploying dualStack OCP clusters for manual verification.

      Acceptance:

      • Manually set up a long-lived dual-stack OCP cluster on PSI/OpenStack, which will be used for running downstream pipeline integration tests. This cluster will be reused across test runs.
      • (Task moved to https://issues.redhat.com/browse/OSSM-9694) Update the downstream pipeline to include dual-stack parameters during the installation of the Sail Operator, as documented here: -https://github.com/istio-ecosystem/sail-operator/tree/main/docs#installation-steps-
      • Currently, not all integration tests are being run on OCP (even for IPv4 clusters) in downstream, and there is a separate Epic to track this. For the dual-stack job, we will execute the same test suite as the regular IPv4 pipeline and expand the test matrix as the QE team adds more tests to the standard pipeline.

       

              mabramov@redhat.com Mikhail Abramov
              sgaddam@redhat.com Gaddam Sridhar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: