Epic Goal

Upgrade the OpenShift Pipelines Console Plugin to be compatible with upcoming OCP changes and enhance test coverage and maintainability.

Why is this important?

• React 18 Upgrade: OCP is planning to adopt React 18 in version 4.22, and our plugin must be compatible to avoid build or runtime issues. This is a breaking change and needs to be developed and tested in a separate branch. The operator has to point to the new branch when OCP supports React@18 for the previous version, it has to point to the 

• PatternFly 6 Upgrade: PatternFly 6 introduces significant breaking changes in components and styling. Upgrading ensures UI consistency and alignment with the rest of OCP.

• E2E for Dynamic Plugin: Strengthens reliability by adding automated end-to-end coverage for dynamic plugin loading and integration scenarios, reducing regression risk during upgrades.

Scenarios

1. The plugin builds and runs successfully with React 18.

1. The plugin UI functions and appearance remain consistent after PatternFly 6 migration.

1. Automated E2E tests validate that dynamic plugins load, register, and render as expected.

1. All CI pipelines pass with updated dependencies and tests.

Acceptance Criteria (Mandatory)

• CI MUST be running successfully with all automated tests passing.

• Release Technical Enablement — Provide necessary release enablement details and documentation, including:

• • Steps to build with React 18 and PatternFly 6

• • Known breaking changes and migration notes

• • Updated dependency versions

• • Validation steps for QA

Dependencies (internal and external)

• Internal:

• • OpenShift Console codebase alignment for React 18 and PatternFly 6.

• • Shared components or hooks used across Pipelines and Console Plugin.

• External:

• • PatternFly 6 official release and migration guides.

• • React 18 compatibility in OCP 4.22 base image and build pipeline.

Previous Work (Optional)

• Existing E2E test framework setup for plugin validation.

Done Checklist

• Acceptance criteria are met.

• Non-functional properties (performance, resource usage, UX, security) validated.

• User Journey automation delivered for dynamic plugin scenarios.

• Support and SRE teams provided with documentation and knowledge to support upgraded plugin in production.