Chapter 2. Installing Fuse Online on OCP 3.11

Installation of Fuse Online on OCP 3.11 requires a cluster administrator to register the Fuse Online custom resource definition and grant installation permission to the appropriate user(s). The user who installs Fuse Online must determine whether to install a default Fuse Online environment or a customized Fuse Online environment. For a customized Fuse Online environment, editing of the default custom resource file is required.

Each installation of Fuse Online is referred to as a Fuse Online environment. In a given OpenShift project, there can be exactly one Fuse Online environment. Each Fuse Online environment has its own URL. In a single OpenShift cluster, there can be multiple Fuse Online environments.

Important

The Fuse Online installation process requires access to registry.redhat.io, which is the Red Hat Ecosystem Catalog for container images. Fuse Online does not support or test the use of external container registries, custom registries, or registries in disconnected environments.

The following topics provide details for installing Fuse Online:

2.1. Overview of the steps required to install Fuse Online on OCP 3.11

To install Fuse Online on OCP on-site, a cluster administrator must perform some tasks and then a user who has permission to install Fuse Online in a particular OpenShift project performs some tasks and runs the installation script. The following diagram shows the workflow:

Workflow for installing Fuse Online on OCP. See outline after this image.

Outline for installing Fuse Online on OCP 3.11 workflow image

To install Fuse Online on OCP, the main steps are:

  1. A user with cluster administration permissions:

    1. Downloads the installation script and related files.
    2. Registers a custom resource definition (CRD) at the cluster level, by using OpenShift oc client tool commands.
    3. Grants permission for one or more users to install Fuse Online in their projects, by using OpenShift oc client tool commands.

  2. For each OpenShift project in which you want to install Fuse Online, a user who is granted permission to install Fuse Online:

    1. Decides whether to install a default Fuse Online environment or a customized Fuse Online environment. A customized Fuse Online environment enables one or more add-on features and/or implements one or more custom configuration settings.
    2. Downloads the installation script and related files.
    3. Optional. Edits the default-cr.yml file (provided in the Fuse Online download package) if a customized Fuse Online environment is wanted.
    4. Optional. Creates an OpenShift secret if an external database for persisting connection and integration definitions is wanted.
    5. Invokes the installation script.
    6. Confirms that Fuse Online is running.

For each OpenShift project in which Fuse Online is to be installed, the cluster administrator must grant permission to a user to install Fuse Online in that particular project.

To install a default Fuse Online environment, the user with permission to install Fuse Online downloads and runs the installation script. No other steps are required.

Additional resource

Fuse Online installation readme file

2.2. Registering a custom resource definition for deploying Fuse Online resources

To enable installation of Fuse Online, a cluster administrator registers a custom resource definition. The administrator needs to do this only once for the OpenShift cluster. Then, for each project in which the administrator wants Fuse Online to be installed, the administrator grants an appropriate user permission to install Fuse Online in that project.

Prerequisites

  • You must have cluster administration permissions.
  • You installed the oc client tool and it is connected to the OCP cluster into which Fuse Online will be installed.

  • On your OCP environment, at least three persistent volumes are available for use by Fuse Online. All of the persistent volumes must have the following configuration requirements:

    • capacity.storage: 1Gi
    • accessMode: ReadWriteOnce

Procedure

  1. Download the package that contains the Fuse Online installation script from the following location:

    https://github.com/syndesisio/fuse-online-install/releases/tag/1.12

  2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.12 directory contains the script and supporting files for installing Fuse Online.

  3. Log in to OpenShift with an account that has cluster admin permissions. For example:

    oc login -u admin -p adminpwd

  4. Confirm that you are properly connected by running the following command, which lists any custom resource definitions that are already registered in this cluster.

    oc get crd

    You are properly connected if there is no error message.

  5. Register the custom resource definition at the cluster level by switching to the fuse-online-install-1.12 directory and invoking the following command:

    bash install_ocp.sh --setup

  6. Confirm that registration was successful by running the following command again:

    oc get crd

    The output list of registered custom resource definitions should include syndesis.

  7. In each project in which you want Fuse Online to be installed, grant installation permission to a user. For each project:

    1. Change to the project in which you want a user to be able to install Fuse Online. For example:

      oc project fuse-online-project

    2. Grant a user permission to install Fuse Online in that project. For example, the following command grants permission to install Fuse Online to developer user. After running this command, the developer user can install Fuse Online in the current project, which is fuse-online-project in this example:

      bash install_ocp.sh --grant developer

      Repeat these two commands for each OpenShift project in which you want to grant permission for Fuse Online installation. A single user can install Fuse Online in more than one project in the cluster. To enable this, change to another project and specify the same user, for example:

      oc project another-fuse-online-project
      bash install_ocp.sh --grant developer

Result

The syndesis custom resource definition is registered in the cluster.

Next steps

Users with permission to install Fuse Online must decide whether to install a default Fuse Online environment or a customized Fuse Online environment.

2.3. When editing the default custom resource is required before installing Fuse Online

The Fuse Online installation includes a default custom resource, which specifies the default settings for configurable Fuse Online environment add-on features and parameter settings.

You need to edit the default custom resource before you install Fuse Online if you want the installed Fuse Online environment to:

  • Use a URL that you specify for the OpenShift route by which the Fuse Online console can be reached. The default is that the installation process calculates this route.
  • Use an external database to store connection and integration definitions. The default is that the environment uses an internal database.
  • Increase the amount of internal storage that is available for persisting connection and integration definitions. The default, which is 1Gi, is sufficient for most Fuse Online environments.

To configure a Fuse Online environment for any one of these behaviors, you MUST edit the custom resource when you install Fuse Online. In other words, you cannot change the configuration of an installed Fuse Online environment to implement any of these behaviors. Also, after you install a Fuse Online environment that is configured for any of these behaviors, you cannot change that behavior in the installed environment.

2.4. Descriptions of custom resource attributes that configure Fuse Online

In addition to the custom resource attributes that you can specify only before installation, there are a number of custom resource attributes that you can change before or after installation.

Table 1 provides a brief description of configurable custom resource settings and indicates when you can change them: before and/or after installation. To achieve the Fuse Online configuration that you want, use the information in this table to determine how you need to change the custom resource before installation or how you want to change it after installation. Then follow the appropriate procedure:

For OCP 4.x:

For OCP 3.11:

Table 2.1. Configurable custom resource settings

Feature/SettingWhen you can set thisSpecification

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 Repositories

Specify external Maven repositories that your Fuse Online environment needs to access.

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.

demoData
Provides a sample PostgreSQL database and a sample database connector.

Set before or after installation

spec:
  demoData: false

If you set the todo addon to true, you must also set the demoData option to true.

ToDo app
For testing sample integrations.

Set before or after installation

spec:
  addons:
    todo:
      enabled: false
When you set the todo addon to true, you must make sure that the demoData option is set to true.
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

About add-on features and configuration settings

  • Enhanced activity tracking

    Activity tracking, using Jaeger, is enabled by default when you install Fuse Online. The Fuse Online installation (from the OperatorHub or the command-line script) detects the existence of the OperatorHub and installs Jaeger by using the OperatorHub’s subscription functionality. For the limited circumstances in which the OperatorHub is not available, Fuse Online uses its own installation functions to install Jaeger. Optionally, you can customize the Jaeger configuration before you install Fuse Online as described in the About configuring Fuse Online for Jaeger monitoring section.

  • External database for persisting connections and integrations

    A default installation of Fuse Online provides an internal PostgreSQL database that Fuse Online uses to persist connection and integration definitions. You can choose to use an external PostgreSQL database instead, such as one of the PostgreSQL templates that OpenShift provides by default.

  • Internal storage capacity

    The default setting of 1Gi is sufficient for most Fuse Online environments. It is expected that you would increase this setting for a new Fuse Online installation only upon the recommendation of Red Hat technical support. That is, you have been running another Fuse Online environment in which you encountered Fuse Online server errors and Red Hat technical support determined that you need to install a new Fuse Online environment with a database volume capacity that is larger than the default.

    To increase Fuse Online internal storage capacity in an OpenShift project that is already running Fuse Online, you must first uninstall Fuse Online. See Uninstalling Fuse Online from an OCP project.

  • Database connection pool configuration

    You can configure the following syndesis-server database connection pool properties:

    • connectionTimeout - The maximum number of milliseconds that the syndesis-server waits for a connection from the pool. The lowest acceptable connection timeout is 250 ms. The default is 30000 (30 seconds).
    • idleTimeout - The maximum amount of time (in milliseconds) that a connection is allowed to sit idle in the pool before the connection is removed. A value of 0 means that idle connections are never removed from the pool. The minimum allowed value is 10000 (10 seconds). The default is 600000 (10 minutes),
    • leakDetectionThreshold - The amount of time (in milliseconds) that a connection can be out of the pool before a message is logged indicating a possible connection leak. A value of 0 means leak detection is disabled. The lowest acceptable value for enabling leak detection is 2000 (2 seconds). The default is 0.
    • maxLifetime - The maximum lifetime (in milliseconds) of a connection in the pool. The minimum allowed value is 30000 (30 seconds). The default is 1800000 (30 minutes).
    • maximumPoolSize - The maximum size that the pool is allowed to reach, including both idle and in-use connections. The default is 10.
    • minimumIdle - The minimum number of idle connections maintained in the pool. The default is the value of maximumPoolSize.

2.5. Editing the default custom resource file before installing Fuse Online

To install a default Fuse Online environment, you do not need to edit the default custom resource file. See Installing Fuse Online on OCP 4.x or Installing Fuse Online on OCP 3.11.

To install a customized Fuse Online environment, you must edit the default-cr.yml file before you install Fuse Online. This file is in the Fuse Online download package. There are some custom resource settings that you can specify only before Fuse Online installation. See When editing the default custom resource is required before installation.

There are other custom resource settings that you can specify before or after Fuse Online installation. See Descriptions of custom resource attributes that configure Fuse Online.

The Fuse Online installation process uses the settings that you specify in the default-cr.yml file to create the syndesis custom resource. The syndesis custom resource settings determine the configuration of the installed Fuse Online environment.

Prerequisites

  • You plan to install and run Fuse Online on OCP on-site.
  • The oc client tool is installed and it is connected to the OCP cluster in which you plan to install Fuse Online
  • A user with cluster administration permissions gave you permission to install Fuse Online in any project that you have permission to access in the cluster.

Procedure

  1. If you did not already download the package that contains the Fuse Online installation scripts:

    1. Download it now from the following location:

      https://github.com/syndesisio/fuse-online-install/releases/tag/1.12

    2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.12 directory contains the scripts and supporting files for installing Fuse Online.

  2. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

    oc login -u developer -p developer

  3. Open the fuse-online-install-1.12/default-cr.yml file in an editor.
  4. Edit the default-cr.yml file so that it enables the features and sets the parameters that you want. To determine what you need to specify, see Descriptions of custom resource attributes that configure Fuse Online.
  5. Save the default-cr.yml file.

Result

The default-cr.yml file contains the configuration specifications for a new Fuse Online installation.

Next steps

If you edited the default-cr.yml file to specify an external database then follow the instructions in Installing Fuse Online with an external database before you install Fuse Online. Otherwise, you are ready to follow the instructions in Installing Fuse Online on OCP 3.11.

2.6. About configuring Fuse Online for Jaeger monitoring

Jaeger is open source software for tracing transactions between distributed services. It is especially useful for monitoring and troubleshooting complex microservices environments.

When you install Fuse Online, either from the OperatorHub or by using the command-line script, the Fuse Online installation detects the existence of the OperatorHub and installs Jaeger by using the OperatorHub’s subscription functionality. For the limited circumstances in which the OperatorHub is not available, Fuse Online uses its own installation functions to install Jaeger.

A default Fuse Online environment configures all needed Jaeger components. Optionally, you can edit the Fuse Online custom resource to specify a client-only/independent server configuration or a hybrid Jaeger client and Jaeger Operator configuration.

Default Jaeger configuration

The basic, out-of-the-box, configuration includes all Jaeger components. You can start learning about how Jaeger works by experimenting with its monitoring capabilities. The default configuration provides a memory-only, limited, backend storage capability.

Installing Fuse Online with the default Jaeger configuration has the following results:

  • Fuse Online components have Jaeger communication URLs.
  • Jaeger Operator is installed.
  • Jaeger custom resource is configured with a default configuration for activity monitoring.

A Fuse Online installation with the default Jaeger configuration, has the following syndesis custom resource specification: 

apiVersion: syndesis.io/v1beta2
kind: Syndesis
metadata:
  name: app
spec:
  addons:
    jaeger:
      enabled: true

When the clientOnly and operatorOnly are unspecified (set to false, by default) Fuse Online uses the provided Jaeger backend as well as the default, memory-only storage provided by the Jaeger server configuration.

Client-only/independent server configuration

With a client-only/independent server configuration, only client URL connections are configured for communication between Fuse Online and an externally configured Jaeger backend. All aspects of the Jaeger backend are external and independent of the Fuse Online environment and syndesis-operator. This includes the Jaeger Operator and the Jaeger custom resource.

To install a client-only Jaeger configuration, edit the custom resource before you install Fuse Online as follows:

For example: 

apiVersion: syndesis.io/v1beta2
kind: Syndesis
metadata:
  name: app
spec:
  addons:
    jaeger:
      enabled: true
      clientOnly: true
      queryUri: https://jaeger-query-hostname:443/api
      collectorUri: https://jaeger-collector-hostname:14268/api/traces

Hybrid Jaeger client and operator configuration

With a hybrid Jaeger client and Jaeger Operator configuration, Fuse Online installs the Jaeger Operator as well as the Jaeger client capabilities. A Jaeger custom resource is not installed. You must install your own Jaeger custom resource, which defines your Jaeger server configuration. This lets you take advantage of the Fuse Online-provided capability and also tailor Jaeger configuration for your own environment, for example, you can use Elasticsearch or Cassandra for data storage.

To install a hybrid Jaeger client and Jaeger Operator configuration:

  • Edit the custom resource before you install Fuse Online as shown in the following example: 

    apiVersion: syndesis.io/v1beta2
kind: Syndesis
metadata:
  name: app
spec:
  addons:
    jaeger:
      enabled: true
      operatorOnly: true

  • Name the Jaeger custom resource syndesis-jaeger as shown in the following example: 

    apiVersion: jaegertracing.io/v1
kind: Jaeger
metadata:
  name: syndesis-jaeger
  ...
spec:
   ....

    Note: Alternately, if you want to use a different name for the Jaeger custom resource, set the queryUri and collectorUri in the Syndesis custom resource as described in the Client-only/independent server configuration section.

When the Jaeger custom resource with syndesis-jaeger name is created, the Jaeger instance collects data from the Fuse Online integrations. By default, you can view this data in the Fuse Online activity log.

2.7. Installing Fuse Online with an external database

If you want to install a Fuse Online environment that uses an external database to persist connection and integration definitions:

  • Create a postgreSQL database with a hostname that the OpenShift cluster can locate.
  • Before you install Fuse Online, create an OpenShift secret named syndesis-global-config for the external database.
  • Install Fuse Online.
  • Before you deploy Fuse Online, edit the custom resource to configure the connection to the external database.

Prerequisites

  • For OCP 3.11 only, you edited the default-cr.yml file to specify the use of an external database to persist connection and integration definitions.
  • Fuse Online is not yet installed.
  • The oc client tool is installed and it is connected to the OCP cluster in which you plan to install Fuse Online.
  • A user with cluster administration permissions gave you permission to install Fuse Online in any project that you have permission to access in the cluster.

Procedure

  1. Log in to OpenShift with an account that has permission to install Fuse Online. For example: 

    oc login -u developer -p developer

  2. Create a postgreSQL database that is available to the OpenShift cluster on which you install Fuse Online and that defines values for the following configuration options:

    • Connection username
    • Database name

    • Database password

      The following example uses one of the PostgreSQL templates that OpenShift provides by default.

      Note: Only use the PostgreSQL ephemeral (postgresql-ephemeral) template for development or testing purposes. For a production environment, use the PostgreSQL (postgresql) template. 

      oc new-app postgresql-ephemeral -p POSTGRESQL_USER=syndesis -p POSTGRESQL_PASSWORD=exdb-pwd -p POSTGRESQL_DATABASE=syndesisdb

      This command returns information about the database that you need when you configure Fuse Online, such as the URL.

      For information about creating a database see the PostgreSQL topic in the OpenShift documentation.

  3. Create and save a resource file (for example, my-fuse-online-secret-cr.yml) that contains the following content: 

    apiVersion: v1
kind: Secret
metadata:
  name: syndesis-global-config
  namespace: my-fuse-online-project
type: Opaque
stringData:
  POSTGRESQL_PASSWORD: exdb-pw

    Replace my-fuse-online-project with the name of the OpenShift project in which you plan to install the Fuse Online environment for which you are specifying an external database.

    Replace exdb-pw with the password from Step 2. Fuse Online will use it as the password for accessing the external database. Note that stringData converts the password value to a base64-encoded value (so that you do not have to do the conversion).

    For information about OpenShift secrets, see Secrets.

  4. Add the secret to the cluster, for example: 

    oc apply -f my-fuse-online-secret-cr.yml

    On the OpenShift cluster, the syndesis-global-config secret is available to a Fuse Online environment that is installed with a custom resource that specifies an external database.

  5. Install Fuse Online in the my-fuse-online-project project that you specified in the YAML file for the secret (in Step 4).

Result

The Fuse Online installation process uses the settings in the custom resource to determine the configuration of the installed Fuse Online environment.

When correctly installed and deployed, Fuse Online brings up all of the required pods except for syndesis-db. Instead of syndesis-db, the syndesis-server connects to the database with the service name of the external database. If the external database configuration is incorrect then the syndesis-server fails to initialize and the Fuse Online deployment ends with an error.

2.8. Running the script that installs Fuse Online on OCP 3.11

The Fuse Online installation script installs a Fuse Online environment according to the specifications in the default-cr.yml file, which is in the Fuse Online download package. To install a default environment, no editing of that file is required. To install a customized environment, you must edit the default-cr.yml file before you run the installation script.

Prerequisites

Procedure

  1. If you did not already download the package that contains the Fuse Online installation scripts:

    1. Download it from the following location:

      https://github.com/syndesisio/fuse-online-install/releases/tag/1.12

    2. Unpack the downloaded archive at a convenient location on your file system. The fuse-online-install-1.12 directory contains the scripts and supporting files for installing Fuse Online.

  2. Log in to OpenShift with an account that has permission to install Fuse Online. For example:

    oc login -u developer -p developer

  3. Switch to the OpenShift project into which you want to install Fuse Online, for example:

    oc project my-fuse-online-project

    Alternatively, when you run the installation script, you can specify, for example, --project my-fuse-online-project.

  4. In the directory in which you downloaded the installation script, invoke the installation script:

    bash install_ocp.sh

    To learn about the installation script options, invoke the bash install_ocp.sh --help command.

  5. Confirm that the syndesis custom resource that syndesis-operator used to install Fuse Online contains exactly the content that you want:

    1. Invoke the following command to display the syndesis custom resource content:

      oc describe syndesis/app

    2. Check the content of the custom resource.

      If it does not contain all of your updates, then there was probably a syntax error in the custom resource. You must uninstall Fuse Online and try again to define a valid custom resource. See Uninstalling Fuse Online from an OCP project.

  6. Confirm that installation was successful:

    1. Display the OpenShift OAuth proxy log-in page at https://openshift-route.

      If you chose to let the installation script calculate the OpenShift route, then the script displays the calculated route near the end of its execution. Replace openshift-route with the value that the script provided.

      If you edited the default-cr.yml file to specify the routeHostname for Fuse Online, replace openshift-route with the route that you specified.

    2. If you are not already logged in to the OpenShift console, its log-in page appears. Enter your OpenShift user name and password to log in.

    The Fuse Online home page appears either immediately or after you log in to the OpenShift console.

Additional resource

Fuse Online installation readme file