Business Problem:

Customer observed for an environment with a large number of clusters, > 120, that Central was not available until all clusters were registered, for over 10 minutes.

Use Cases:

Customers would be reassured that things are happening, even if requests return 0 or fewer than the number of expected entities until all clusters are registered.

Key Functionality:

Bring up the API and UI immediately while Central catches up with the secured clusters in the background.

• API requests can return 0, or whatever number of entities have been discovered so far during the startup process. (MVP of returning 0; stretch goal of making the running total available)
• UI can be logged into, and users would see 0, or whatever number of entities have been discovered so far during the startup process.
• Customer could start created integrations, policies, importing policies, setting system preferences while Central is still registering clusters.

Benefits:

Greater assurance that Central is working, and fewer "cry-wolf" support inquiries.

Acceptance criteria:

1. Central API becomes available in a reasonable amount of time (1 minute max, stretch goal of 30 seconds)
2. Central UI login screen becomes available shortly after API (within 1 minute of API being ready, stretch goal of within 30 seconds of API being ready)
3. User could login to

Implementation Suggestions (optional):

• Integration: tbd

• Dependencies: tbd 

• User Experience:
  • API and UI become available in a reasonable amount of time, even if no entities have yet been processed for the environment;
  • possible message banner that clusters are still be processed until some flag is set that all known clusters have been registered
  • no other new specific API or UI functionality

Timeline:

tbd

Please use the following Jira fields to complete this Feature Request

1. [Jira Field] Summary Required: [Provide a clear and concise name/description for the feature]
2. [Jira Field] Description:
3. [Jira Field] Component:
4. [Jira Field] Priority: [Indicate the importance or urgency of the feature on a scale of High, Medium, or Low]

1. [Jira Field] Supporting Documentation:
    

1. [Attach any relevant documents, research, or supporting materials that provide additional context or information]