Epic Goal

Ensure that disabling the Pipelines Console Plugin through the OpenShift Web Console completely removes the associated pipelines-console-plugin Deployment

Why is this important?

Currently, when a user disables the Pipelines Console Plugin through the console, the plugin disappears from the UI as expected, but the backend Deployment persists and is continuously recreated by the operator.
This causes confusion for administrators who expect the plugin to be fully removed and may lead to resource waste or undesired operator behavior.
Having a clean enable/disable flow improves:

• Operator manageability and transparency

• Cluster resource hygiene

• Alignment between Console UX and Operator state

• Supportability and debugging clarity for customers and Red Hat support teams.

Scenarios

1. Enable Plugin (Current Behavior)

• • Admin enables the Pipelines Console Plugin from the OpenShift Web Console.

• • Pipelines Operator deploys the pipelines-console-plugin deployment in openshift-pipelines.

• • Plugin appears in the console as expected.

1. Disable Plugin (Proposed Fix)

• • Admin disables the Pipelines Console Plugin through the console settings.

• • Operator detects the change (via Console Operator config or custom config CR).

• • Operator removes the associated Deployment and resources for the plugin.

• • The plugin no longer appears in the UI

1. Re-enable Plugin

• • Admin re-enables the plugin from the console.

• • Operator redeploys the pipelines-console-plugin deployment cleanly.

• • No leftover state from previous deployment interferes.

Acceptance Criteria (Mandatory)

• Disabling the Pipelines Console Plugin via the OpenShift Web Console results in the removal of the corresponding Deployment from openshift-pipelines.

• Re-enabling the plugin recreates the deployment and restores functionality.

• Operator reconciles correctly with the Console Operator configuration (or equivalent mechanism).

• No residual pods, services, or configuration remain after disabling.

• CI pipelines for this feature run successfully with automated tests validating enable/disable behavior.

• Documentation and release enablement material are updated to guide admins on this behavior.

Dependencies (Internal and External)

• Console Operator — provides the source of truth for enabled/disabled plugins.

• Pipelines Operator — responsible for creating/removing the deployment based on configuration.

• OCP Web Console — UI trigger for enabling/disabling the plugin.

• OLM (Operator Lifecycle Manager) — may need updates if CRD or config mechanisms are changed.

Done Checklist

• Acceptance criteria are met.

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

• CI automation covers enable/disable scenarios.

• User journey validated (from console to operator to deployment state).

• Support and SRE teams are provided with documentation and troubleshooting guidance for plugin enable/disable lifecycle.

• Release notes and admin guides updated accordingly.