Dynamic Gateway Server deployment

Gateway Server can be deployed dynamically by configuring it in the custom resource (CR) of the FTM operator. The configuration includes a name for the Gateway Server deployment, the type of Gateway Server, and the Gateway Server properties configuration file to use. By default, a dynamic inbound Gateway Server and a dynamic outbound Gateway Server are deployed.

To add another dynamic Gateway Server to the deployment, you must update the custom resource to provide the following parameters for each Gateway Server that you want to deploy.
name
The name to use for this deployment of the Gateway Server.
configure
The name of the Gateway Server configmap created by the user to use for this deployment of the Gateway Server. The Gateway Server properties file for this deployment of Gateway Server must be created and added to the configmap by using the config.properties key. For more information, see Customizing FTM components.
type
The type of this dynamic Gateway Server. The type is either Inbound, Inbound-check or Outbound.

The operator creates the Red Hat® OpenShift® deployment object for each of the configured Gateway Server names and mounts the configuration file in the Gateway Server container.

Default dynamic Gateway Server deployment

The default Gateway Server inbound and inbound-check pod is configured to use Business Rules Server. This inbound and inbound-check pod contains both a Business Rules Server and a Gateway Server container.

The following custom resource YAML example shows the configuration for the default dynamic Gateway Server deployment.
gateways:
  - type: Inbound
    name: gateway-server
  - type: Inbound-check
    name: gateway-server
  - type: Outbound
    name: gateway-server
  - type: Inbound
    name: gateway-server-custom
    configure:
      configmapName: ftm-gateway-server-custom-config
Note: Do not update or delete these default gateway-inbound, gateway-inbound-check, and gateway-outbound roles that are defined in the custom resource. The gateway-inbound-check role is used in Check only.