Epic Goal

Implement findings that will help Search handle the ACM high scale 3500 managed SNO.

Why is this important?

Customers expect an ACM hub to provide observability of the fleet. Search presents the best UI way to Navigate to a specific resource when you have thousands of SNO nodes and related resources under management.

Scenarios

As a central IT admin, I need to find the failing resources via Search interface.

As an edge IoT admin, I need to find failing nodes, images, deployments and fetch real-time YAML and Logs data.

In all scenarios, I should expect that I have a high number of nodes under management, into the ~3500 range.

Acceptance Criteria

• Search components at the hub and the managed cluster should remain stable as the scale of nodes approaches 1000, 2000, 3000, 3500.
• Search can have additional documentation to describe what changes are necessary in order for high scale to be achieved.
• Customers will ask 'how much data' is being sent across the network - it would be reasonable that we are measuring the data load on a network as the scale increases.
• Customers will ask for 'tuning/performance' data and it is reasonable that we should be able to document it with our findings.
• Search metrics should be able to help us visualize the resource consumption.
• Search can emit alerts based on certain critical health conditions.

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 - Downstream documentation merged: <link to meaningful PR>

ACM Epic Done Checklist

See presentation and details.

Update with "Y" if Epic meets the requirement, "N" if it does not,  or "N/A" if not applicable.

• _ FIPS Readiness
• _ Works in Disconnected
• _ Global Proxy Support
• _ Installable to Infrastructure Nodes
• _ No impacts to Performance and Scalability
• _ Backup and Restorable