Deploying an App Build using Flogo Provisioner

This topic describes how to deploy a Flogo application to a data plane using the Flogo Provisioner. Before you begin, ensure that you have created an app build. To learn how to create an app build, see Creating and Deploying a New App Build.

    Procedure
  1. In the Deploy App dialog, click Deploy app in the Managed By Flogo Provisioner card.

    Tip: You can access the Deploy App dialog in two ways:
    1. If you have just created an app build, select Deploy App on the Finished tab.

    2. In the App Builds section, click the menu next to the app you want to deploy, and then select Deploy.

  2. On the Resource Configurations tab, specify the values for the following fields:

    Field Description
    Application Name

    Specify the name of your application.

    Default: The application name is automatically retrieved from the uploaded .flogo or .json file.

    Note: When naming your application, ensure that the name contains only lowercase letters (a-z), numeric characters (0-9), and hyphens (-). Hyphens must be placed in the middle of the name, not at the beginning or end. For example, abcdefg, 123458, abcd458, or 12-ab-4 are valid. Any other characters, such as uppercase letters, spaces, or special symbols, cause the deployment to fail.
    NameSpace

    Before specifying a namespace in this field, ensure that you have created it. As you type, the field autosuggests a list of existing namespaces.

    Tip: If you type a non-existing namespace, it suggests the commands to create it in your data plane.
    Note: If no namespace is specified, the default namespace of the data plane is used.

    A data plane can have multiple namespaces, which are linked to a service account of the respective data plane. To create a namespace other than the default data plane namespace, see Deploying App Outside Data Plane Namespace.

    Application Tags

    Click the icon to add tags for your application to enhance searchability and categorization.
  3. To enable auto scaling for the app, turn on the Auto Scaling Configuration toggle and specify the values for the following fields:

    Field Description
    Minimum Replica

    The minimum number of replicas for the app. Hover over the current number and use the arrows to change it.

    Default: 1

    Maximum Replica

    The maximum number of replicas for the app. Hover over the current number and use the arrows to change it.

    Default: 2

    Target CPU Utilization (%)

    Target CPU utilization is the desired average CPU usage percentage that triggers scaling actions to maintain optimal performance.

    If the actual CPU utilization exceeds the configured target CPU utilization percentage, auto scaling increases the number of app pods to handle the increased workload. If usage drops below the target percentage, auto scaling scales down the app pods.

    Default: 70

    Target Memory Utilization (%)

    Target memory utilization is the desired average memory usage percentage that triggers scaling actions to ensure that the system maintains sufficient resources.

    If the actual memory utilization exceeds the configured target memory utilization percentage, auto scaling increases the number of app pods to handle the increased workload. If usage drops below the target percentage, auto scaling scales down the app pods.

    Default: 70

  4. To configure the app resources, specify the values for the following fields:

    Field Description
    CPU Requests

    Specify the minimum CPU resources required for optimal container performance.

    Note: CPU resources are measured in CPU units, where 1 CPU unit equals 1 physical or virtual core, depending on the node type.

    Default: 250 m

    CPU Limits

    Specify the maximum CPU resources that a container can use within a pod. This limit prevents the container from exceeding its allocation and impacting other pods on the same node.

    Default: 500 m

    Memory Requests

    Specify the minimum amount of memory required for the container to function properly. Kubernetes prioritizes scheduling pods onto nodes with sufficient memory to meet these requests.

    Enter an integer value, measured in memory units (MiB, GiB, or TiB).

    Default: 512 Mi

    Memory Limits

    Specify the maximum amount of memory a container can use within a pod.

    Enter an integer value, measured in memory units (MiB, GiB, or TiB).

    Default: 1024 Mi

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

  6. Click Deploy App.

ResultThe Flogo application is deployed on your data plane. On the Finished tab, you can click the respective buttons to view app builds, view deployed apps, or view app details.
Note: Apps deployed using the Flogo provisioner APIs cannot be managed using the Helm Chart APIs. You can manage these apps using the Flogo Provisioner APIs for Application Management and Application and Build Management APIs.