1. I'd propose to title this OpenShift Cloud Init or Cluster Init

2. Propose to add a field to the OCM API that allows for passing a chunk of YAML with an "initial manifest" to a newly provisioned cluster (or maybe a path to an object storage?) as a method to "glue" cluster provisioning into configuration automation using something like GitOps.

3. Multiple customers have asked for a way to give their new clusters a very basic set of configurations so they can transition them directly to using GitOps, especially customers who are using IaC tools to build their clusters. The key point is not needing to leave their IaC environment (e.g. Terraform) to pass to another tool to do initial config so they can then pass cluster config management to their GitOps tooling.

4. This would presumably impact the OCM API (which would need to accept the YAML and/or an object storage path), as well as the installer, which might need to schedule a Job to retrieve and apply the YAML to the API once the cluster was up.

The idea was that like `cloud-init` on EC2 instances that it be up to the customer to make sure it's correct.