Story (Required)

As a user trying to use GitOps I want to use GitOps console plugin on all GitOps supported versions.

In order to keep a consistent behavior of Environments page, GitOps console plugin should be working on all GitOps supported versions.

Background (Required)

OCP v4.15.0 is a release where the user can still fall back to the static plugin if the dynamic plugin isn't installed. From OCP v4.15.0 the static plugin will be automatically toggled off when console loads dynamic plugin (GITOPS-3574), and only dynamic plugin Environments button will be displayed in the left menu on the Developer page. On OCV v4.15.0, both the static plugin and the dynamic plugin are available and in case the dynamic plugin is not working as expected, user is able to toggle on the static plugin by setting `GITOPS_DYNAMIC` flag value to `false` through feature flags.

When the static plugin gets removed completely from console, the dynamic plugin should be available as a default option on the GitOps Installation page. So the default value of DYNAMIC_PLUGIN_START_OCP_VERSION should be changed to the lowest version supported by GitOps.

Out of scope

<Defines what is not included in this story>

Approach (Required)

Decide on when the static plugin should be completely removed from console code and make sure this story is done on the same release static plugin get deleted.

Dependencies

GITOPS-3575 gets released.

Acceptance Criteria (Mandatory)

• Environments Page is loading and working on all GitOps supported OCP versions, and only one Environments button is displayed on the Developer page.
• GitOps CI test is updated and passing after DYNAMIC_PLUGIN_START_OCP_VERSION gets updated.

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