Normal Epic Goal
Review existing Bill of Materials for OCM and determine which components should be incorporated or documents as a recommended pattern (not be confused with a validated pattern).
Why is this important?
This answers the question of do we offer our customers the same tools and processes that we (Red Hat) uses to manage our fleet of clusters.
Components
- Fleet Manager (Not needed)
- ACM is a fleet manager
- App Interface (Not needed)
- Policy and App fill this role
- Vault
- Addon Operator (not needed)
- Addon Service (not needed)
- ClusterService (self service provisioning of AWS Hive, AWS HCP, & HCP Hive
- Account Management Service (include)
- This will be the core inventory used to link ClusterService and Maestro together
- Backplane (investigate)
- RDS
- ClusterService
- Account Management System
- Fleet Manager (not needed)
- Service Log
- Service Log client
- Service Log
- Cert-manager
- s3 OIDC Configuration
- quay.io
- registry.redhat.io
- registry.connect.redhat.com
- ss.redhat.com
- RHOBS (already included, but can we include SREP dashboard??)
- Telemetry (already present, but different metrics)
- Console (already present)
- Splunk forwarding client config
- Logging Splunk
- Cloud watch AppSRE
- cloud watch for customers
- Email SendGrid
- console.openshift.com & api.openshift.com (will be included as part of NEW Inventory & Maestro APIs)
- Sentry??
- GitLab (not needed)
- Jira (not needed)
- Managed Services Service
- DB
- Loki
- Hive (already included)
- Dynatrace
...
Acceptance Criteria
Review each item in the list and determine:
1. Include
2. Document pattern
2.1 Note a list of BYO options
3. Not needed at all
Previous Work (Optional):
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>