Epic Goal

Review the AppInt. projects and determine:
1. Benefit to ACM customers

2. Could be included in ACM as part of the AppInterface transport layer.

2.5 I think Maestro might also be a candidate for transport

Why is this important?

Re-use tooling our SRE team has build, use what we build.

AppInterface Components

• OSD/ROSA cluster management - Create/destroy/upgrade?
• network management - AWS and GCP specific
• namespace management - (review and compare to policy and Gitops options)
• configuration and secret management - Configuration is Policy in ACM, what type of configuration is present here.  Secrets through vault, external secrets??
• cloud assets management - This is moving to Kessel Common Inventory
• continuous and progressive delivery
• and much more

it also comes with capabilities to enable teams to successfully run their services, including: * access management (openshift/aws/cloudflare/github/gitlab/quay/more)

• communication management (email/slack/pagerduty/schedules/code/more)

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):

1. XCM BOM: https://docs.google.com/spreadsheets/d/1dy-sai6xx-W1s6xUY8tCQz2C9TazstKiaS12Jd-KKO8/edit#gid=1491824188

Done Checklist

• List of AppInterface capabilities with PROs & CONs