OCP Console team made a decision in 4.19, to replace VirtualizedTable component with PF's DataView component. This decision was strongly was mainly influenced by the fact that the PF's VirtualizedTable which Console is using under the hood is has been deprecated.

In 4.19 OCP Console team deprecated VirtualizedTable and ListPageFilter and useListPageFilter. Also mmarosi123 created a POC: Use DataView component for Console Pods list page in which he demonstrated how the migration could look like. Here is a summary of the findings from the POC:  https://docs.google.com/document/d/1gC2dvp7pCRR2_OLhyxgadtqA2-7fBN3gl2ZlWhaJzWY/edit?usp=sharing

This epic should contain all the migration work OCP Console team would be capable to carry out though out 4.20. Since the Console codebase contains also Static Plugins and Dynamic Demo Plugin which are using VirtualizedTable we should plan to migrate these as well at some point. In case of Static Plugins the change should be carried out by the plugin owner.

Acceptance Criteria

1. Core Console UI

• • All primary list pages (Pods, Deployments, etc.) render via DataView.

• • Filtering, sorting, pagination, bulk-select, row actions, and contextual menus behave equivalently or better than before.

• • No remaining imports or runtime warnings related to VirtualizedTable, ListPageFilter, or useListPageFilter.

• • All existing list-page tests are updated or replaced to assert correct DataView behavior.

1. Dynamic Demo Plugin

• • Demo plugin list pages refactored to use DataView.

• • Documentation/examples updated accordingly.

1. Static Plugins

• • A published “DataView Migration Guide” is available in the Console docs.

• • Each static-plugin owner has an open ticket/PR tracked in this epic.

• • No static plugin in the v4.20 branch still imports VirtualizedTable or uses the deprecated filter hooks.

1. Update automated tests to cover the new implementations.

Open Questions:

1. Should OCP Console team create a wrapper around the DataView component, which we could reuse across the codebase and potentially expose it to the plugins via SDK