Skip to main content


Version Changes (5.6.0-5.7.0)

Interpretation of main function points:

1. Plugin sharing and one-click installation

For the operation, maintenance and management capabilities of business containers, Rainbond implements a plug-in mechanism through the sidecar in the pod.Developers can develop plug-ins by themselves, and enable and configure plug-ins as needed according to business needs. The current plug-ins can already achieve:

  • Extend the functionality of components without changing existing business code
  • Complete some data initialization operations before the business runs
  • Send business logs to external servers for analysis and processing
  • Intercept the traffic of cleaning business and use it as a firewall
  • Monitor business performance indicators, etc.

However, in the previous version, after a user created a plug-in under a team and needed to use it for another team, he needed to manually create it again and set the corresponding configuration items.This increases the threshold for users to use to a certain extent. Now, like apps, we can also support sharing and one-click installation of plug-ins after supporting the sharing and click installation of

applications.When you have made a plug-in available under a team, you can share it through Rainbond's local component library or open source application store.Other users can install and use it through component libraries and open source app stores.The advantage of this is that plug-ins can also be accumulated and reused like applications, and plug-ins developed by community users can also be shared with other users.


2. Extend the configuration capabilities of the plug-in

When the plugin itself needs a corresponding configuration file or storage, the user needs to manually add storage to the component.This is because the storage is shared between plugins and components, but when a plugin is used for multiple components, it is necessary to configure storage under each component, which causes configuration complexity. Now users can configure the storage and configuration files required by the plugin at runtime directly in the shown below:


In this way, when the user activates the plug-in for the component, the corresponding storage and configuration file can be automatically created for the component.Reduced configuration complexity.

3. Support for docking with Ceph

Stable and reliable storage is the most important part of using Kubernetes in production.Kubernetes provides a mainstream storage volume access solution (In-Tree) by default, and also provides a plug-in mechanism (Out-Of-Tree) to allow access to third-party storage that implements the CSI interface. In the current version, by extending the CSI The ability can perfectly dock Ceph.

Detailed change points

new features

  • [Plugin management] Support plugin sharing and installation

  • [Plugin management] Support plugins to define storage and configuration files individually

  • [Component management] Source code construction supports nodejs16 version

  • [Application Management] Support applications to be sorted by update time and running status

  • 【Storage】Support ceph storage via CSI

Optimization function

  • [Component management] Optimize the default container of the web terminal as the component container

  • [Installation] Optimized environment detection and prompts when installing the dind version

  • [Installation] Optimize the environment check and prompt during helm installation

  • 【Team View】Optimize the response speed of team view

  • [Component Management] Optimized the problem that the disk usage is too large when the component log is too large

  • 【Enterprise management】Add team resource display in enterprise view

  • [Component management] Optimize the performance problems caused by the resource limitation of the built-in mesh plugin

BUG fix

  • [Gateway] Fixed the problem that the new policy does not take effect when there are too many gateway policies

  • [Component Management] Fix the problem that component resource monitoring does not take effect

  • [Component Management] Fix the server-side exception caused by the gateway path policy

  • [Team Management] Fixed the problem that the team list cannot be displayed due to the deletion of the team creator

  • [Enterprise Management] Fix the problem that Oauth authorization automatically expires

  • [Component Management] Fixed the problem of empty instances in third-party components

  • 【App Management】Fixed the issue that the published app does not display the log

  • [Plugin management] Fixed the problem that after the initialization type plugin is uninstalled, the plugin will not be cleared after the component is updated

  • [Plugin management] Fixed the problem that the environment variables configured in the startup command of the plugin do not take effect


Thanks to the following users for their participation and feedback in the community, in order to make the product better, we welcome any form of participation and contribution.