Description

The OpenShift Console currently renders the Guided Tour feature unconditionally. This has caused flakiness in Console E2E (Cypress) tests running in CI, as the guided tour can interfere with UI interactions and timing.

To address this and to give cluster administrators explicit control, the Console API should expose a Guided Tour capability flag that allows the feature to be enabled or disabled at the cluster level.

This story focuses on API-level support and operator wiring required to expose this capability to the Console frontend.

Motivation

• Reduce Console CI flakiness caused by Guided Tour overlays

• Allow cluster admins to opt in/out of Guided Tours

• Provide a consistent capability-based mechanism aligned with other Console features

• Enable test environments to explicitly disable Guided Tours

Scope

• Introduce a new GuidedTourFeature capability in the Console API

• Ensure the capability is configurable and surfaced to the Console

• Vendor the API changes into console-operator

Acceptance Criteria

• Add new console-operator config API, a new capability named GuidedTourFeature

• API changes are vendored into console-operator and update operator-console.yaml by adding the Enabled/Disabled capability