Feature Overview

Detect the applications deployed without gitops

Goals

Apps deployed with helm without gitops show in RHACM

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

oc create ns my-project
namespace/my-project created
helm repo add toto https://charts.example.com/toto
helm install my-nginx toto/nginx --namespace my-project

Questions to answer

• ...

Out of Scope

• …

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

• ...

Customer Considerations

• ...

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)?
  Minimal changes - this may make it into the recent changes but I don't see this requiring documentation.

• Does this feature have a doc impact?
  no - minimal

• New Content, Updates to existing content, Release Note, or No Doc Impact
  release note.

• 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)?
  Monitor their app deployments with RHACM
• 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)?
  release notes, don't think there is new content to be added.