Story (Required)

As OpenShift Pipelines moves through rapid release cycles, we must guarantee "N-1" compatibility and state persistence. A common customer pain point is the behavior of active or completed PipelineRuns during an Operator/Platform upgrade. This story adds a test suite that deliberately triggers workloads on a "pre-upgrade" version and performs comprehensive status verification "post-upgrade" to ensure no data loss or state corruption occurs in the Tekton CRDs.

Approach (Required)

Start Pipelineruns before the upgrade and verify the pipelinerun for succefful completion post upgrade

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met