Modify servicesSubnet and serviceNetworkCIDR in OpenShift

Issue

• Customer needs to have application (inside OpenShift) access an application (external to OpenShift) that is running on an IP address that falls within the servicesSubnet range for their OpenShift Cluster. The only way to correct this would be to change the servicesSubnet and serviceNetworkCIDR values, which appears to be unsupported as well as breaking various service if you change it on a currently running cluster.
• We have an application that requires connectivity to an external service with the same subnet as the configured servicesSubnet and serviceNetworkCIDR in our OpenShift deployment.