Epic Goal

Support the display of many thousands of applications in the Application list, without requiring users to search for specific applications. This will require performing aggregation of the applications list in the console backend to provide an API that supports pagination with sorting, filtering, and searching.

Why is this important?

Users may not always know the name of the application they want to view, or may want to browse a set of applications that is still larger than the limits allowed by the current implementation, even after certain filters are applied.

Scenarios

A user with tens of thousands of discovered Argo CD, OCP, or Flux applications uses the Application list without any truncation or requirement to enter search text or select filters.

Acceptance Criteria

• Any number of applications can be viewed without truncation or prompting to add filtering
• Only the data for the current page view is loaded in the browser to avoid overwhelming the client in terms of memory or processing

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.