Upgrading an App
This feature is used to update the application, application properties, application connectors, and version without a restart of the application.
- Procedure
-
In TIBCO Control Plane, click Data Planes from the left navigation.
-
On the Data Plane card of your choice, click Go to Data Plane.
-
In the Applications section, click the Flogo app that you want to upgrade from the listed apps.
-
On the upper-right corner, click menu
.
-
Select the
Upgrade Application option.
Note: This option is available only for applications managed by Flogo Provisioner. This option is not available for the applications deployed using a Helm chart. To manage the apps deployed using a Helm chart, see Helm Chart APIs for Application Management. -
On the Upload Files tab, either drag and drop the
.json
or.flogo
file into the box, or click browse to upload to upload a file from your system. Then, click Upload Selected File.Note:-
The file upload is optional. You are not required to upload a file. You can update the contribution details without updating the application details.
-
To deploy an app created locally in Visual Studio Code, upload the
.flogo
or.json
file available in your workspace.
-
-
Click Next.
-
On the Select Versions tab, specify the values for the following fields:
Field Description Application Details Application Build Name Specify the name of your application.
Default: The application name is automatically retrieved from the uploaded
.flogo
or.json
file in Step 6.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
, or12-ab-4
are valid. Any other characters, such as uppercase letters, spaces, or special symbols, cause the deployment to fail.Flogo Version From the Flogo version dropdown, select the Flogo version that you want to work with.
Default: The latest version or provisioned version.
Application Tags Click the icon to add tags for your application to enhance searchability and categorization.
Select Connectors/Custom Extensions version Refresh List Click to fetch the latest list of connector/extension versions.
Default: The latest version or provisioned version.
<Connector/Extension> Choose the version of the connectors and custom extensions that you want to use with your application.
If your application requires a connector that is not currently provisioned in the data plane, you are prompted to provision it. Click the provision the missing connector in another tab link. For more information, see Provisioning Flogo and Connectors.
-
Select the I have read and accepted the TIBCO End User Agreement (EUA) checkbox to accept the End-User Agreement.
-
Click Next.
-
On the Resource Configuration tab:
-
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
-
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
-
-
Click Upgrade App.