Installing API Connect in a single namespace on OpenShift
Use individual subsystem CRs to install API Connect subsystems in a shared namespace on OpenShift.
About this task
API Connect subsystems are installed by creating individual subsystem CRs in the same shared
namespace. If you want to install your API Connect subsystems in different namespaces, for example
Management server in a namespace that is called mgmt, and gateway in a namespace
that is called gway, then see: Installing API Connect subsystems in different namespaces or environments on OpenShift.
Air-gapped installations: If you are installing API Connect in an offline environment, first follow the steps for configuring the catalog sources as described here: Air-gapped installation.
Attention: If you want to configure FIPS support for API Connect, you must enable FIPS
on the cluster as part of the initial OpenShift deployment. You cannot modify an existing cluster to
enable FIPS support. For more information, see Configuring FIPS support on OpenShift.