1. Proposed title of this feature request: Retain VPC hosting the cluster
2. What is the nature and description of the request? During cluster uninstallation, provide a means for customers to retain the VPC created as part of the OpenShift cluster.  
3. Why does the customer need this? (List the business requirements here)

a. During cluster uninstallation, both the cluster and the VPC created during the installation that hosted the cluster are deleted. If other VPC resources are created in the cluster, the deletion of VPC removes these resources. Customers want to retain these VPC resources that belong to other workloads. 

b. Customers benefit from the ease of cluster installation creating a VPC but end up creating additional clusters or resources in the same VPC because of lower overheads of placing trusted resources within the same VPC. Without the requested enhancement, they'd need to dedicate the VPC to the cluster and place any resources that the cluster connects with outside the VPC so their life cycle are independent. 

c. A lot of OpenShift features sometimes require reinstallation of clusters (e.g., expanding machine-cidr, modifying AWS Tags, or EC2 Instance Metadata Service version to name a few) that decoupling the cluster life cycle from the VPC life cycle would help to retain other VPC peering or Transit GWY connections. This would simplify cloud operations vastly. 

 
4. List any affected packages or components.

Installer.