Application-layer new-cluster automation

[ralphbean]

One thing that's up in the air here is dealing with the valero backup key. I assume that is waiting on some new work to be done in the cluster-level automation and can be followed up on later.

This is ready for review.

[manish-jangra]

@ralphbean If you're referring to kms key for the velero backup in the description of this PR, we will not use that anymore for new environments as we're creating s3 bucket (for velero backup) using the default s3 encryption managed by aws itself. We can always change that if we need to and change terraform module to create kms key for the velero backup.

[ralphbean]

@manish-jangra ah, thanks for the tip about the valero key - that is what I was referring to. I'll drop those comments in the yaml and update the description here.

[manish-jangra]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: manish-jangra, ralphbean

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [manish-jangra,ralphbean]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment