Chapter 1. Installing Fuse Online on OCP 4.x

Enhanced activity tracking

Additional information about enhanced activity tracking follows this table.

Set only before installation

addons:
  jaeger:
    enabled: true
    clientOnly: false
    operatorOnly: false

Enhanced activity tracking is enabled, by default. If you want to customize the Jaeger configuration, you can set clientOnly or operatorOnly to true.

External database

Additional information about using an external database follows this table.

Set only before installation

spec:
  components:
    database:
      externalDbURL: postgresql://custom-postgres:5432
      user: db-user-name
      name: db-name

Replace custom-postgres:5432 with the host name and port for a PostgreSQL database.
Replace db-user-name with the name of a user account that can access that database.
Replace db-name with the name of the database.

Internal storage capacity for connections and integrations.

Ignored if you also specify an external database.

Additional information about increasing internal storage follows this table.

Set only before installation

spec:
  components:
    database:
      resources:
        volumeCapacity: 1Gi
        volumeName: my-volume

Replace 1Gi with the amount of storage you need. The default is 1Gi.

Replace my-volume with the name of the volume to use for internal storage. This parameter is optional.

OpenShift route for accessing Fuse Online console

Set only before installation

spec:
  routeHostname: project.route.com

Replace project.route.com with the OpenShift route by which the Fuse Online console can be reached.
For example: north-project.6a63.fuse-online.openshiftapps.com

Memory and CPU

Increase the default amount of memory that is available to one or more components.

Each component defines its own memory requirement, which means that each pod has a limit on the amount of memory it is assigned. For information about limit and request settings, see the section on Configuring cluster memory to meet container memory and risk requirements in the OpenShift documentation.

You can also specify CPU resources for the server component.

The database component is the internal database that stores connection and integration definitions.

The meta component provides the business logic, such as the connectors, which the server loads.

The prometheus component monitors Fuse Online infrastructure components and Fuse Online integrations.

Set only before installation

components:
  server:
    resources:
      limit:
        memory: "1024Mi"
        cpu: "800m"
      request:
        memory: "512Mi"
        cpu: "500m"
  meta:
    resources:
      limit:
        memory: "750Mi"
      request:
        memory: "300Mi"
  database:
    resources:
      limit:
        memory: "300Mi"
      request:
        memory: "300Mi"
  prometheus:
    resources:
      limit:
        memory: "750Mi"
      request:
        memory: "750Mi"

3scale discovery

Expose APIs for Fuse Online API provider integrations so that they are discoverable by Red Hat 3scale.

More information: Configuring Fuse Online to enable 3scale discovery of APIs.

Set before or after installation

components:
    server:
      features:
        managementUrlFor3scale: https://url-for-3scale

Specify the URL for your 3scale user interface.

Backups

Additional setup steps are described in Backing up a Fuse Online environment.

Set before or after installation

spec:
  backup:
    schedule: interval

Replace interval with the desired duration between backups. Use cron utility format for intervals and predefined schedules. Do not specify the @ sign in front of the interval.

Node affinity and tolerations

Determines the placement of Fuse Online infrastructure component and integration pods onto nodes within the cluster.

Node affinity allows you to specify an affinity for Fuse Online pods towards a group of nodes to be placed on.

Tolerations allows you to control which nodes the Fuse Online pods run on and to prevent other workloads from using those nodes.

See also: Configuring Fuse Online pods.

Set before or after installation

Note: Use infraScheduling for Fuse Online infrastructure component deployments. For Fuse Online integration deployments, replace infraScheduling with integrationScheduling.

spec:
  infraScheduling:
    tolerations:
      key: value
      operator: value
      effect: value

spec:
  infraScheduling:
    affinity:
      nodeAffinity:
        preferredDuringSchedulingIgnoredDuringExecution:
          weight:
          preference:
            matchExpressions:
              key: value
              operator: value
              values:
                value1,
                value2

Integration limit

Specify the maximum number of running integrations. The default, 0, does not limit the number of running integrations.

Set before or after installation

components:
    server:
      features:
        integrationLimit: 0

Database connection pool

You can adjust the server connection pool configuration to manage the connections to the database.

Additional information about the database pool configuration follows this table.

Set before or after installation

components:
  server:
    connectionPool:
      connectionTimeout: 30000
      idleTimeout: 600000
      leakDetectionThreshold: 0
      maxLifetime: 1800000
      maximumPoolSize: 10
      minimumIdle: 10

Java Options

You can specify Java options for the syndesis-server and syndesis-meta components.

Depending on the Java option, you can specify different values for the components. For example, you can set a JVM-related parameter for syndesis-server only, because it requires more computer resources than syndesis-meta.

Set before or after installation

components:+   server:
    javaOptions:
      -option_name=my_value   meta:
    javaOptions:
      -option_name=my_value

Replace -option_name with the Java option name. You can specify any Java option prefix (-D, -X, or -XX).

Replace my_value with value for the option.

For example, to configure the HTTP proxy: components:+   server:
    javaOptions:
      -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800   meta:
    javaOptions:
      -Dhttp.proxyHost=10.0.0.100 -Dhttp.proxyPort=8800`

Maven Arguments

Specify additional Maven options to use when building Fuse Online integrations.

Set before or after installation

components:
    server:
      features:
        maven:
          additionalArguments:
            "typeA=stringA typeB=stringB"

For example:
          additionalArguments:
            "-Dhttp.proxy=my_proxy -DpropA=valueA"

Maven Mirror

Specify the single repository from which you want Fuse Online to access Maven artifacts when it builds integrations. Ignore the Maven repositories that Fuse Online would access by default. This option is typically used when you install Fuse Online in a restricted environment.

Set before or after installation

components:
    server:
      features:
        maven:
          mirror: https://customRepo

Replace `https://customRepo with the URL of the repository.

Maven Repositories

Specify external Maven repositories that your Fuse Online environment needs to access, in addition to the Maven repositories that Fuse Online accesses by default.

Set before or after installation

components:
    server:
      features:
        mavenRepositories:
          customRepo1: https://customRepo1
          customRepo2: https://customRepo2

Replace customRepo with the name of a repository.
For each repository, specify its URL.

Monitoring

See also: Monitoring Fuse Online integrations on OCP with Prometheus.

Set before or after installation

addons:
  ops:
    enabled: true

Public REST API

Additional set-up steps are described in Exposing Fuse Online public REST API endpoints for use by external tools.

Set before or after installation

addons:
  publicApi:
    enabled: true
    routeHostname: public-syndesis.192.168.64.63.nip.io

Set routeHostname to the public address for invoking Fuse Online REST API endpoints. Your cluster setup determines the public address that you need to specify. In the previous example, the route host name is valid for a minishift cluster.

ToDo addon
Provides a sample integration application for testing purposes, an AMQ Broker, as well as a sample PostgreSQL database and a sample database connector.

Set before or after installation

spec:
  addons:
    todo:
      enabled: false
For installing Fuse Online in a restricted environment, you must make sure that the todo addon is set to false (the default) before installation. After installing Fuse Online , you can optionally download the todo application from https://github.com/syndesisio/todo-example and follow the steps in the Readme file, changing the repository URL to a location available on your private network.

See also Adding sample data to a Fuse Online environment running on OCP.

Auditing

For viewing basic changes made to connectors, connections, and integrations.

See also Auditing Fuse Fuse Online components.

Note: This is a Technology Preview feature.

Set before or after installation

components:
  server:
    features:
      auditing: true