Skip to main content

Generic data initialization plugin


Project address:

This is a plugin for initializing data, suitable for all cloud platforms based on Kubernetes system including Rainbond.

The basic principle is realized by using the init container of Kubernetes.The container where the plug-in is located will run until the completion of the service container. Through the defined download and decompression logic, the pre-prepared initialization data compression package (only supports three formats of zip, tgz, and tar.gz) will be decompressed to the target directory. Go, the download process supports breakpoint resume.Of course, we have to set the target directory to be persistent in advance.

The environment variables required by the plugin are configured as follows:

FILE_URLurlInitialization file download address
FILE_PATHpath to dirWhen a single directory is initialized, specify the persistent directory address; when multiple directories are initialized, specify /
EXTRACT_FILEtrue/falseThe initialization file is automatically decompressed by default
DOWNLOAD_ARGS-X ,--xxExtra command line arguments for wget
LOCK_PATHpath to dirLock file save path, specify any existing persistent directory
DEBUGanything trueEnable debug log

Building plugins in Rainbond

In Rainbond's plug-in mechanism, there is natural support for the init container - the initialization type plug-in.

1. Create a new plugin

2. Fill in the build source information

Key information includes:

Next, click Create Plugin and wait for the build to succeed.

3. Declare the plugin configuration

In this step, we need to declare what kind of configuration this plugin can receive.From the overview section, we know that there are several environment variables that need to be defined for this plugin to work properly.

Enter the configuration group management, add a group of configuration:

After saving the configuration, the plugin is ready.

How to use plugins

1. Prerequisites

  • The service components that need to be initialized data have already set up the persistence directory.
  • The persistent data has been packaged (supported formats zip, tgz, tar.gz) and uploaded to object storage.

2. Install and configure the plugin

  • Install the pre-made generic data initialization plugin for the service component.
  • View the configuration, enter the download address (FILE_URL) of the initialization data package, the target persistence directory (FILE_PATH), and the lock file storage directory (LOCK_PATH), and then update the configuration.
  • Update the memory, because the initialization type plug-in will automatically exit after running, so you don't have to worry about occupying too much resources.The setting of the memory value can be enlarged as much as possible, and it is appropriate to be slightly larger than the size of the persistent data packet.This will speed up the download and decompression.

3. Build and start the service component

Observe the log, if the output is as follows, it means that the data initialization process has started:

7b554df4b7bb:Connecting to (

7b554df4b7bb:data.tgz 0% | | 367k 2:45:46 ETA

After waiting for the download and decompression to complete, the service component will enter the normal startup process.

4. Remove the plug-in

The plug-in has the permission to read and write the persistent data directory of the service component. Although we have added the implementation logic to prevent repeated initialization, we still strongly require to uninstall the plug in after the data is initialized successfully.

How to initialize multiple directories

The above basic usage method can initialize data for a specified directory.However, in practice, it may be necessary to initialize data for multiple directories at the same time, and multiple directories do not belong to the same parent directory.For example, it is necessary to initialize data to /app ,/data/a , and/root/.b 3 directories at the same time.

In response to such a situation, we can solve this problem from the perspective of data packaging.Through the specified packaging method, all data is packaged into the same compressed package, and after downloading and decompressing, it is directly decompressed into each directory.

Packing is as follows:

tar cvzf data.tgz /app /data/a /root/.b

Store the packaged file and upload the object to get the download URL, such as

When operating in the Rainbond platform, the process is roughly as follows:

  • Persist all 3 target directory settings
  • Install the generic data initialization plugin
  • Fill in FILE_URL and use the URL just obtained
  • Fill in, its value is This is the most critical step
  • Fill in LOCK_PATH, its value must be an existing persistent storage path
  • Start the component to start the initialization process

About lock files

After the first initialization is completed, a hidden file, the lock file, will be generated under LOCK_PATH.Subsequent restarts will recognize this lock file, and if it exists, skip the initialization process.The purpose of this is to avoid duplicating initialization data.

About object storage

We recommend placing the initialization package in object storage and providing a download address that the Rainbond platform can access.

Common self-built object storage has the following two situations

-Object storage software based on the S3 protocol, such as Minio, can be searched and installed after Rainbond is connected to the open source application store.

  • Object storage services provided by public cloud service providers, such as Alibaba Cloud OSS.