Managing a Flex Runtime
Boomi Flex Runtime is part of Boomi's Early Access program, which offers beta versions of Boomi innovations on an "as is" basis, with no warranties. These features are not final production releases, are unsupported under Boomi's service agreements and support services, and are not intended for production use. While Boomi will work to address issues encountered during the preview and welcomes participant feedback, any feedback provided — whether ideas, suggestions, code, or recommendations, oral or written — is irrevocably assigned to Boomi, LP. By participating, you confirm you have the authority to provide that feedback, will not assert any intellectual property claims against Boomi, and that Boomi may freely implement it without violating any party's rights. If a beta feature doesn't meet Boomi's standards or raises significant concerns, it may never reach general availability, and Boomi cannot guarantee any particular innovation will be released in a supported form. Note that some innovations may only be available as open source or for specific runtime configurations. Documentation may be provided as PDFs, online, or on Community forums.
Refer to the Early Access page to view current programs and request Early Access for a specific feature.
Managing workloads
Adding a workload
In the Boomi Platform > Runtime Management screen, select a Flex runtime. In the detail page, go to the Workloads tab.
Workloads can be added anytime after installation. The runtime must be installed and online to add and set up a new workload.
You can also select workloads during initial runtime creation — refer to Installing a Flex Runtime
- Click Add workload.
- Select one or more workloads available to your account.
- The workload appears under the Pending Setup section.
- Click Setup. Enter configuration for the workload if required (not all workloads have setup configuration).
- The runtime automatically downloads and configures the workload. When complete, the workload appears under Application workloads with status Online.
The workload is now ready to use.
Note: The ingress endpoint required for the Agent step is a runtime-level setting, not something configured per workload — refer to Configuring your runtime's ingress endpoint below.
Updating a workload
You can trigger an update of a workload (app or system) from the UI. A banner is displayed when an update is available for a given workload. To update it, click the Update button, review the new version info, and click OK.
Removing a workload
For Early Access, removing a workload isn't yet available from the Boomi Platform UI. You do this manually at the infrastructure level in your Kubernetes cluster.
Operations
Deleting a runtime
For Early Access, deleting a runtime isn't yet available from the Boomi Platform UI. You do this manually at the infrastructure level in your Kubernetes cluster.
Starting, stopping, and restarting a runtime
For Early Access, starting, stopping, and restarting a runtime isn't yet available from the Boomi Platform UI. You do this manually at the infrastructure level in your Kubernetes cluster.
Status
Runtime status
The runtime is considered healthy if the runtime is communicating with the platform and all its workloads (app and system) are healthy. Statuses roll up from Workload service >> Workload >> Runtime. For example, if one of the Agent workload's services has an error, the Agent workload shows as Degraded, and the overall runtime shows as Degraded.
| Entity | Status | Meaning |
|---|---|---|
| Runtime | Pending install | Your Flex Runtime has been created in the Boomi Platform, but the physical runtime has not been installed yet. Upon successful installation, the status will automatically update to Online. |
| Runtime | Online | Your Flex Runtime is running, communicating with the platform, and all workloads are healthy. |
| Workload | Pending Setup | The workload has been added and is awaiting user action. Click Setup to complete configuration. |
| Workload | Pending | Setup is complete, and the runtime is downloading and configuring the workload automatically. |
| Workload | Online | The workload has finished provisioning and is running. |
Configuration
Configuring your runtime's ingress endpoint (required for the Agent step)
Your Flex Runtime normally only makes outbound connections to the Boomi Platform — no inbound access is required. The one exception is the Agent step: to support it, other systems need a way to reach your runtime, so you must manually configure your runtime's ingress endpoint after installation. This isn't generated automatically — an empty value is a valid default, and your runtime installs and runs normally without one; only Agent step functionality depends on it.
Where to set the endpoint
In the Boomi Platform, enter the address that the runtime running the Agent step uses to reach your runtime's ingress gateway from outside your cluster. Agent Control Tower retrieves this address from the Runtime Management service to build an OpenAPI spec for the Agent step. This happens entirely on the platform side — Agent Control Tower never connects to your Flex Runtime directly.
What value to enter
The correct value depends on the load balancer or ingress you set up in Preparing your Kubernetes cluster for Flex Runtime. Enter it as scheme, host, and optional port only — no path and no trailing slash.
The address must resolve and be reachable from the runtime running the Agent step — not from the machine you're configuring this on. Agent Control Tower doesn't need network access to your Flex Runtime; it retrieves the address from the Runtime Management service (platform-side) to build the OpenAPI spec used by the Agent step.
For example: https://runtime.yourcompany.com — reachable from wherever that hostname resolves for the atom running the Agent step.
