OCPMCP-29: Adding ACM setup script

[matzew]

Adding setup scripts for Hub cluster creation and importing new managed clusters

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew

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 [matzew]

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

[matzew]

/assign @Cali0707 this can be tested with "dev cluster" and maybe cluster-bot

[matzew]

/retitle: OCPMCP-29: Adding ACM setup script

[openshift-ci-robot]

@matzew: This pull request references OCPMCP-29 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Adding setup scripts for Hub cluster creation and importing new managed clusters

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[matzew]

/retitle OCPMCP-29: Adding ACM setup script

[Cali0707]

@matzew can you add some kind of OPENSHIFT_DEVELOPMENT.md (so we don't conflict with any upstream DEVELOPMENT.md) that explains how to use these targets? In particular, the different env vars needed

[matzew]

/test images

[matzew]

can you add some kind of OPENSHIFT_DEVELOPMENT.md

@Cali0707 Absolutely! That is exactly the plan, once I have all the bits together.

I did these initial ACM related install scripts first to get some smaller, narrowed focus going.

[openshift-ci]

@matzew: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.