Description of problem: Some customers are requiring the possibility to have a static IP due to security reasons like "I am receiving some data from a vendor and they require IP address", and "In order to configure the firewall of the email server to accept emails from Openshift Online ( https://abc.pro-us-east-1.openshiftapps.com )I would need a public IP of my Openshift Online service" At the moment we do not have any single subnet, or list of subnets that would adequately describe the IP space in which any of our hosts may appear other than to say it's always going to be in the IP space of an AWS host in that region. You could refer to this document in which Amazon publishes their public IP ranges, but at the moment there are 103 ranges published for us-east-1 so I very much doubt it's suitable for the usage requested. - http://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html Our environment doesn't permit us to determine a limited IP or range for a given pod at this time.
The ask here is likely to bring https://docs.openshift.com/container-platform/3.7/admin_guide/managing_networking.html#admin-guide-limit-pod-access-egress-router and https://docs.openshift.com/container-platform/3.7/admin_guide/managing_networking.html#enabling-static-ips-for-external-project-traffic to online.
There is no way for us to enable this feature for OpenShift Online end-users.