A flow app is a generic flow application. A flow is represented as a tab within the Node-Red editor workspace and is the main way to organize nodes.

To create one:

  1. Go to the Browse menu on the left

  2. Scroll down and click on Flow to start the flow application

General Info

This is the first configuration page and contains the following parameters:

Parameter

Type

Description

Version

drop-down

Version number of the application you want to deploy. By default it is set to the latest version.

Space

drop-down

The namespace where you want your application to be deployed

Cluster

drop-down

Kubernetes cluster where the app would be deployed. It is only shown when you have the same Space created on more than one cluster.

App Name

text field

How the app will be called in the Apps menu

Tags

text field

Tags you want your application to be associated with

Set the Version (optional), Space, Cluster (optional), App Name, and Tags (optional) and click Next to proceed to the next screen

Infrastructure

Parameter

Type

Description

Repository

text field

The repository from where you can pull the image

Tag

text field

Tag of the image

Pull Policy

drop-down

The pull policy of the image.

  1. IfNotPresent - the image is pulled only if it is not present locally

  1. Always - the image is pulled every time the pod is started

  1. Never - the image is assumed that exists locally and no attempt to pull is made.

Name of the Registry Secret

text field

Provides the registry secret, that will be used for authentication when pulling the images from the configured repository

The Port for Internal Communication

text field

The port which would be used for internal communication to this pod

Minimum CPU Usage

The minimum CPU resources are allocated for this pod.

Default value is 50m which is equal to 50 millicpu so it would allocate minimum of 0.05 CPU cores to this pod. https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/

Maximum CPU Usage

The maximum CPU resources allocated for this pod.

Default value is 300m which is equal to 300 millicpu so it would allocate minimof um 0.05 CPU cores and maximum of 0.3 CPU cores to this pod. https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/

Minimum Memory Usage

The minimum memory allocated for this pod.

Default value is 50Mi which is equal to 50 mebibytes so it would allocate minimum of 50*1024^2 bytes. https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/

Maximum Memory Usage

The maximum memory allocated for this pod.

The default value is 150Mi which is equal to 150 mebibytes so it would allocate maximum of 150*1024^2 bytes to this pod. https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/

….

Click on the YAML button in the upper right corner to switch between form-based configuration and text based configuration.

It is safe to leave all the settings in this page with their default values.

Click on Next would bring you to Access Management.

Access Management

Here you need to define who can access this flow application.

Make sure you select a group to which your qibb user belongs, otherwise you would be cut out of it and you wouldn’t be able to make any changes on the flow app, after it gets deployed.

Summary

The Summary section provides a quick overview of the most important settings and a possibility to change any of the settings before starting the deployment of the flow application.

When you are sure you have configured properly the application you can proceed with its deployment by clicking on the Deploy button.

Deployment

This is the last step, when the application is deployed.

Detailed Deployment Log

Click on the Show Details button to preview the notifications generated during the deployment.

When the app is deployed a Go To App button will be shown which redirects to the App overview page.

Next Steps

As a next step you need to import the flows.json file to deploy the application.