Rancher users install Rainbond

Rancher users install Rainbond

This article is for users who are using Rancher or have some knowledge of Rancher

Rancher, a successful open source project in the Kubernetes ecosystem, is positioned as "Run Kubernetes Everywhere". Rancher can help developers quickly build cloud, edge, and end multi-dimensional Kubernetes clusters, and provide a UI-based management system for multiple cluster resources.

Rainbond is positioning "Enterprise Application Lifecycle Management", similar to Rancher's positioning statement should be "Run Application Everywhere". Rainbond open source users have always faced a flaw, that is, the open source version of Rainbond does not provide for cluster monitoring and visual management. Therefore, combining Rancher is a solution in an open source scenario. For Rancher users, you may try to use Rainbond to manage your applications, and you will feel that it is not as efficient and simple as Rancher. By reading Rainbond related documents, you will find Rainbond's unique product charm in serving enterprise application development, application operation and maintenance, and application delivery.

Next, it will take you to complete the installation of the Rainbond system on Rancher.


  1. Have a stable and usable Rancher environment, if you haven t yet, you can refer to the Rancher installation and deployment documentation
  2. The Kubernetes cluster has at least 4GB of free scheduling memory
  3. Kubernetes version is 1.13 and above
  4. The Kubernetes cluster has at least one node whose port 80/443 is not occupied

start installation

Add Rainbond Operator to the app store

Add Rainbond Operator to Rancher's app store.

1. On the App Store page, click Add App Store

2. Enter the name (such as Rainbond-Operator) and store the URL address inputhttps://gitee.com/rainbond/rainbond-operator

Rancher will search for the existing Helm Chart in the designated code repository. Due to domestic network reasons, use the address of rainbond-operator in gitee.

4. Choose Helm v3 for Helm version

The Rainbond-operator chart uses the Helm v3 specification definition, so the Helm v3 version must be selected.

5. Click Create to complete the application store addition.

6. Go back to the application store page, click Start

7. Click Refresh . After Rancher finishes synchronizing, you can see the newly added Rainbond Operator.

Install Rainbond Operator

Start Rainbond Operator in Rancher.

1. Click the identified rainbond-operator Chart to start Chart installation.

2. Modify the namespace torbd-system

Note that the current namespace can only be set to install rbd-systemaccording to the default configuration of rainbond-operator Chart.

3. Click Start , it will jump to the application list page, and the waiting rainbond-operatorstate is reached Active.

This process will obtain the relevant image of rainbond-operator from the public network, so its startup time greatly depends on your network environment.

Visit the Rainbond installation UI to improve the cluster configuration

rainbond-operator after the completion of exposure to start 30008providing cluster configuration and installation process UI display service. So please visit to IP:30008enter the Rainbond Operator UI page.

The configuration items include mirror warehouse configuration, database configuration and storage configuration. Please consider whether to provide the above services according to the actual situation of your environment (we recommend self-service for high-availability production environments). Of course, Rainbond will automatically install the above services by default.

The other two key configurations are the choice of sum . By default, Rainbond will automatically select a suitable management node for Kubernetes. The gateway node installs the rbd-gatewaygateway service, so it needs to occupy 80, 443such key ports. As the node for Rainbond to build the image, it is best to choose a node with sufficient storage and computing resources. If the above two configuration items do not get the default values, for example, when there are no 80nodes with free ports in your cluster , you may need to perform the following operations:

  1. Use the IP address to search for other available nodes and select.
  2. If a cluster node is no longer available, for example, you have only one node and is already installed Ingress Controller, then you can modify Ingress Controllerthe hostNetworkport is set to false, or modify its non-80, 443. Then re-install Rainbond. If multiple nodes may consider Ingress Controllerexpulsion from a node, so that the port resources to Rainbond use.

Once configured, you can click the configuration is complete, begin the installation . During the installation process, Rainbond will obtain all required images and upload them to the local mirror warehouse, and then start all Rainbond components. This process takes about a 20minute, depending on your network environment.

Rainbond operation and maintenance reference based on Rancher

During the installation and use of Rainbond, Rancher can be used to operate and maintain Rainbond. For example Rainbond , Rainbond .

View the running status and logs of each component of Rainbond

On the workload page, find the namespace rbd-systemand view the status, events, and logs of each component of Rainbond. It can also monitor the workload of a certain component in real time, including CPU, memory, network packets, etc. If a component is abnormal, you can use the above information to troubleshoot; if necessary, you can upload it to the community , or submit Issues to Rainbond-Operator

Expand Rainbond's components on demand

When the load of a Rainbond component is too high, you can use Rancher to increase the number of copies of the component and share some load; relatively, you can use Rancher to reduce the number of copies of the Rainbond component.

When you need to troubleshoot Rainbond components, you may need to modify the startup parameters or environment variables of the components. At this time, you can use Rancher to modify.

Understand the advantages of Rancher users using Rainbond

  • No need to deeply learn how to use all kinds of Kubernetes resources

    Rainbond uses the cloud native application model to provide users with an intelligent and simple application development management model. Whether it is a simple application or a complex microservice architecture, the entire development and deployment process does not require developers to learn Kubernetes-related knowledge in depth.

  • Standard cloud-native 12-element application management model

You may have heard of the 12 elements of cloud native as the current recommended cloud native application development model. The Rainbond application model fully implements the 12 elements of cloud native. Using Rainbond will naturally make your code meet the cloud native requirements.

  • From source code to cloud

Common development languages (Java, PHP, Python, Golang, NodeJS, .NetCore) do not need to define Dockerfile, and do not need to define the Kubernetes deployment method to complete continuous construction and continuous deployment.

  • Standard application multi-cluster delivery

Rainbond provides a variety of ways for developers to quickly deliver applications in multiple clusters and multiple environments to obtain a SaaS-based application delivery experience.

  • Microservice architecture

Rainbond has a built-in ServiceMesh micro-service architecture governance framework. All deployment components are managed according to the micro-service governance ideas, and the micro-service governance functions are available out of the box.

Reference video


common problem

  • Can Rancher's deployed applications be directly taken over by Rainbond

This question is the question of most users, and we hope that Rainbond can automatically take over the applications deployed by Rancher. Unfortunately, because Rancher, the same type of platform, currently does not follow standard specifications (such as OAM ) when deploying applications on the same type of platform , it is difficult for us to convert Rancher's deployed applications into Rainbond application models with 100% compatibility. Therefore, we still recommend users to directly use the source code and image-based rapid redeployment applications provided by Rainbond (compared to manual intervention and optimization after partial conversion, it saves time). At the same time, it is also convenient for users to understand the mechanism and process of Rainbond application management in this process.

  • Can Rainbond deployed applications be managed from the Rancher view

The resources deployed by Rainbond to the Kubernetes cluster are created, upgraded, and recycled by the Rainbond controller, using the resource creation specifications defined by Rainbond. We do not recommend that users modify these resources directly in Rancher. However, observations can be made, such as log observations, resource monitoring observations, and so on.

  • Will Rainbond and Rancher compete in the same direction?

There is a certain crossover between the two products in terms of function, but each has its own focus. Especially on the open source route, we will definitely avoid repetitive wheel building, and at the same time, combine the excellent solutions of the community as much as possible to provide users with a complete value experience.