User Story

As a Customer of ROSA/OSD I want the ability to use dedicated tenancy instances in AWS to give me added security and the benefits of being on physically isolated hardware, thru the VPC tenancy for my instances.

Relevant documentation:

https://docs.openshift.com/container-platform/4.10/machine_management/creating_machinesets/creating-machineset-aws.html#machineset-dedicated-instance_creating-machineset-aws

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-instance.html

As Red Hat offering this option, we present the option thru the selection of the VPC and the machine-pool scope for the tenancy selection.

A customer could select tenancy at cluster creation time for the entire cluster, by selecting a VPC with dedicated tenancy.

The default remains shared tenancy and the new option would be dedicated tenancy.

Acceptance Criteria

• A cluster can be created with the selection of a VPC with dedicated tenancy using the CLI, Terraform and the ROSA/OSD provisioning wizards.
• This feature is documented for OSD/ROSA.

Default Done Criteria

• All existing/affected SOPs have been updated.
• New SOPs have been written.
• Internal training has been developed and delivered.
• The feature has both unit and end to end tests passing in all test
  pipelines and through upgrades.
• If the feature requires QE involvement, QE has signed off.
• The feature exposes metrics necessary to manage it (VALET/RED).
• The feature has had a security review.* Contract impact assessment.
• Service Definition is updated if needed.* Documentation is complete.
• Product Manager signed off on staging/beta implementation.

Dates

Integration Testing:
Beta:
GA:

Current Status

GREEN | YELLOW | RED
GREEN = On track, minimal risk to target date.
YELLOW = Moderate risk to target date.
RED = High risk to target date, or blocked and need to highlight potential
risk to stakeholders.

References

Links to Gdocs, github, and any other relevant information about this epic.