Feature Overview

Support the use of AI tooling for Operational tasks in a multicluster environment.

Goals

Ensure RHACM is able to use AI tools to manage key operational tasks, including but not limited to:

• Log analysis
• Anomaly Detection
• Capacity Forecasting
  • Optimisation Recommendations
• Troubleshooting
  • Incident detection
  • Failure Prediction
  • Support and "chatbot" style querying (Natural Language)
• Auto-Remediation Suggestions
• Root Cause Analysis (RCA)
• Intelligent scaling
• Incident Correlation Timelines
• Region-Aware Optimisation
• Upgrade analysis
• UI support
• MORE?

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

See above.

Questions to answer

• How can RHACM use other existing tools (add-ons?) to perform these tasks?

Out of Scope

• Owning the AI tools; RHACM should be able to be the executor of the AIOps tooling without being the owner.

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• A lot of teams within Red Hat are building these tools for single cluster scenarios. 

Customer Considerations

• Ensure customers see a smooth execution across product features so that when they choose to use AIOps in a multicluster environment the choice does not need to be more than the multicluster tooling (RHACM) and they will get multiclusterized Ops with AI for "free" with it.

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?