Description of problem:

During cluster creation,the user selects Cluster privacy as "private" and checks both "Install into an existing VPC" and "Configure a cluster-wide proxy" checkboxes under Virtual Private Cloud (VPC) section. Once the user changes the Cluster privacy as "public", the checkbox "Install into an existing VPC" is disabled and unchecked whereas the "Configure a cluster-wide proxy" checkbox is checked. This is wrong behavior i.e. Cluster wizard allows users to configure cluster-wide proxy without an existing VPC configuration being checked.

How reproducible:

 Always (100%)

Steps to Reproduce:

1. Start cluster creation wizard for OSD CCS cluster.
2. Under Networking section > Cluster privacy , select "Private"
3. Under Networking section >  Virtual Private Cloud (VPC) , select both "Install into an existing VPC" and "Configure a cluster-wide proxy" checkboxes.
4. Under Networking section > Cluster privacy , select "Public"
5. View the behavior and proceed to the next step.

Actual results:

In Step 4, after choosing cluster privacy to "Public", the checkbox "Install into an existing VPC"  is unselected and disabled but "Configure a cluster-wide proxy" is selected.

Users are allowed to proceed further step and shown cluster-wide proxy configuration window without choosing an existing VPC.

Expected results:

In Step 4, Once the user selects cluster privacy to "Public", both checkboxes i.e "Install into an existing VPC" , "Configure a cluster-wide proxy" should be selected.

"Install into an existing VPC" should be disabled as well . The Wizard should allow the user to make changes against the "Configure a cluster-wide proxy" checkbox but shouldn't allow the user to proceed further without choosing an existing VPC.

Additional info:
Please find the attached screen capture.