In OpenShift Container Platform 4.2, you can perform an installation that does not
require an active connection to the internet to obtain software components. You
complete an installation in a restricted network on only infrastructure that you provision,
not infrastructure that the installation program provisions, so your platform selection is
If you choose to perform a restricted network installation on a cloud platform, you
still require access to its cloud APIs. Some cloud functions, like
Amazon Web Service’s IAM service, require internet access, so you might still
require internet access.
Depending on your network, you might require less internet
access for an installation on bare metal hardware or on VMware vSphere.
To complete a restricted network installation, you must create a registry that
mirrors the contents of the OpenShift Container Platform registry and contains the
installation media. You can create this registry on a mirror host, which can
access both the internet and your closed network, or by using other methods
that meet your restrictions.
Restricted network installations always use user-provisioned infrastructure.
Because of the complexity of the configuration for user-provisioned installations,
consider completing a standard user-provisioned infrastructure installation before
you attempt a restricted network installation. Completing this test installation might
make it easier to isolate and troubleshoot any issues that might arise
during your installation in a restricted network.
Clusters in restricted networks have the following additional limitations and restrictions:
The ClusterVersion status includes an
Unable to retrieve available updates
By default, you cannot use the contents of the Developer Catalog because
you cannot access the required ImageStreamTags.