Installing API Connect subsystems in different namespaces or environments on OpenShift
Install API Connect subsystems in different namespaces, for example Management subsystem
in a namespace that is called apicmgmt, Gateway in a namespace called
apicgway. These same steps can also be used for installing subsystems in different
environments.
About this task
- Installing the API Connect operator with global scope - This document provides you further information on this approach to install API Connect subsystems.
- Setting up multiple namespaces with separate API
Connect operators - You can set up multiple namespaces, each with
its own API Connect operator.
When you install multiple operators in different namespaces, make sure all of them are the same
version. You can use different versions only during an upgrade, but aim to upgrade the operators
together or as close to each other as possible.
The API Connect operator pods in your operator namespace must have network access to the namespace where your API Connect subsystems are installed. Do not configure OpenShift network policies that block communication between any of these namespaces:
- API Connect operator
- API Connect subsystems (operands)
- cert-manager
- openshift-operator-lifecycle-manager
- ibm-common-services
For more information, see Installing operators.
For information about single namespace installation, see Installing API Connect in a single namespace 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.