Provisioning and Upgrading TIBCO Flogo Capability

TIBCO Flogo® (formerly known as TIBCO Flogo® Enterprise) enables AI orchestration and intelligent automation through a visual flow designer integrated into Visual Studio Code. Built on a high-performance Go (Golang) engine, it delivers superior runtime efficiency, an ultra-light memory footprint, fast startup, and low-latency processing across edge, cloud, serverless, and on-premises environments. With its AI-ready architecture and powerful set of connectors, Flogo® transforms enterprise data into intelligent, event-driven, AI-ready workflows.

By provisioning the TIBCO Flogo® capability, you can deploy, manage, and monitor TIBCO Flogo applications using the TIBCO® Control Plane.

For more information, see TIBCO Flogo® documentation and TIBCO Flogo® Extension for Visual Studio Code documentation.

Building Flogo Applications in a Data Plane

Each time you trigger an application build, the Flogo capability creates a separate Kubernetes job in the data plane to perform the build. The build job allocates resources independently of the flogoprovisioner pod, allowing multiple builds to run in parallel without competing for the provisioner's resources. The build job is removed after the build completes.

Build execution is internal to the data plane. There is no change in how you trigger a build or in the resulting application image.

Configuring Resources for the Build Job

You can configure the resources and time limits for the build job. If the capability was provisioned from the Control Plane, set the parameters in the capability YAML file used to provision the capability. If the capability was installed using the Flogo Helm chart, set the parameters in the chart's values.yaml file.

CPU values use Kubernetes CPU units, such as 2000m for two cores. Memory values use Kubernetes memory units, such as 1.5Gi.

Parameter	Description
FLOGO_APP_BUILD_CPU_REQUEST	CPU reserved for the build job. The job is scheduled only on a node that can satisfy this request, so it also determines how many builds can run in parallel on the available worker nodes.
FLOGO_APP_BUILD_CPU_LIMIT	Maximum CPU the build job can consume. Leave this empty for no upper limit, allowing the job to use available CPU on the node.
FLOGO_APP_BUILD_MEMORY_REQUEST	Memory reserved for the build job. Increase this value for large applications that fail to build or are evicted because of insufficient memory.
FLOGO_APP_BUILD_MEMORY_LIMIT	Maximum memory the build job can consume. Leave this empty for no upper limit. If the build exceeds a configured limit, Kubernetes terminates the job and the build fails.
FLOGO_APP_BUILD_TIMEOUT_SECONDS	Maximum time, in seconds, that a build job can run after it starts. If the build does not complete within this period, the job is terminated and the build is marked as failed.
FLOGO_APP_BUILD_MAX_QUEUED_SECONDS	Maximum time, in seconds, that a build job can remain queued while waiting to be scheduled. If the job is not scheduled within this period, the build fails.

Provisioning TIBCO Flogo Capability

Procedure

1. In TIBCO Control Plane, click Data Planes from the left navigation.

2. On the Data Plane card of your choice, click Go to Data Plane.

3. In the Capabilities section, click Provision a capability.

4. On the Provision TIBCO Flogo® card, click Start.

5. Select the required Storage Class and Ingress Controller to provision the capability.

   • If there are no existing storage resources, you can add a storage resource. For more information, see Managing Resources.

6. Click Next.

7. Enter the path prefix in the Path Prefix text box for the ingress resource used to provision public APIs.

8. (Optional) To disable the fluentbit sidecar deployment for the Flogo applications, turn off the Deployment of fluentbit sidecar for Application logs toggle. By default, this toggle is turned on.

9. (Optional) To add custom Fluent Bit configuration, refer to Configuring Fluent Bit for TIBCO Flogo in a Dataplane.

10. Select the I have read and accepted the TIBCO End User Agreement (EUA) checkbox to accept the End-User Agreement.

11. Click Next.

12. On the Provsion Capability tab, you can optionally customize the recipe configuration to adjust the provisioning settings for your Flogo capability. Any changes you make in this section will override the default values when the capability is provisioned. This allows you to fine-tune resource allocations or other provisioning parameters based on your environment's specific requirements.

13. Click Provision Flogo Version.

    It takes some time to provision the capability.

Upgrading TIBCO Flogo Capability

Procedure

1. In TIBCO Control Plane, click Data Planes from the left navigation.

2. On the Data Plane card of your choice, click Go to Data Plane.

3. On the TIBCO Flogo® Capability card, click Upgrade Capability.

4. Verify that the required Storage Class and Ingress Controller are selected.

   • If there are no existing storage resources, you can add a storage resource. For more information, see Managing Resources.

5. Click Next.

6. Review the Path Prefix in the text box for the ingress resource used to provision public APIs.

   Note: Path Prefix is read-only and cannot be modified at this step.

7. Review the Deployment of fluentbit sidecar for Application logs toggle settings for TIBCO Flogo Edition applications.

   • The toggle reflects the setting from when the capability was provisioned. You can modify the toggle settings at this step if needed.

8. Select the I have read and accepted the TIBCO End User Agreement (EUA) checkbox to accept the End-User Agreement.

9. Click Upgrade Capability.

   The capability is upgraded.