Goal: 

• As a member of the Pidone team, I want to have a single, unified place to easily and repeatably deploy RHOSO 18 with Code-Ready Containers (CRC) so I can have a single, consistent way to deploy RHOSO that is well-known and well-documented.

Currently, we will typically do our deployments of RHOSO either by hand through the install_yamls repository and running the targets in the Makefile there or through our collection of existing Jenkins jobs. The Jenkins jobs, while effective, are opaque to a new engineer as to which ones do what and where to begin and the Makefile from the `install_yamls` repository require manual running.

The overall goal of this will be to have a single place that can be used for "standard" deployments with a few options available to tweak your deployment in small ways.  

Acceptance Criteria:

• There is a new Jenkins job that is well-named and clear in intent.
• The job will, given a server, will clean up any previous deployment and then deploy RHOSO using existing jobs and tools as a base line.