Installing the IBM App Connect Operator

You can install the IBM App Connect Operator in either of these installation modes:

• A cluster-wide installation into all namespaces on the cluster (cluster-scoped): Selecting this mode installs the IBM App Connect Operator into the openshift-operators namespace. You install the Operator only once in the cluster and it becomes available to all namespaces (and users) on the cluster. You can then use the cluster-scoped IBM App Connect Operator to deploy and manage App Connect instances or resources within any namespace. This mode is the default option and is generally preferred because it allows you to have a single point from which to control the Operator.
• Installation into a specific namespace on the cluster (namespace-scoped): Selecting this mode installs the IBM App Connect Operator into a single namespace of your choice. With this installation mode, you can install the Operator multiple times, across multiple namespaces, in the same cluster, and at different versions. However, it is not advisable to install different versions of an Operator across namespaces because it can result in conflicts with the custom resource definitions (CRDs) that are used to create App Connect resources. CRDs are not unique to a namespace, but affect the whole cluster, so any conflicts might lead to installation or upgrade issues for an Operator and the resources that it manages. You can use a namespace-scoped IBM App Connect Operator to deploy and manage App Connect instances or resources within that namespace only.