Rainbond (CloudHelp) Installation and Optimization Guide

The article introduces Rainbond (formerly CloudHelp), a Kubernetes‑based CI/CD platform aimed at small‑to‑medium enterprises, and compares it with the earlier Crane project, noting its more active open‑source development.

FAQ

Q: What is the positioning of the open‑source version? A: It is a CI/CD platform for SMEs and a production‑grade application management platform that lets developers focus on code and operations focus on resources. Q: Why release an open‑source version? A: To let more enterprises and hobbyists benefit from container and cloud technologies and to showcase the product’s design philosophy. Q: Development plan for the open‑source version? A: Emphasize stability, keep the design simple and usable, and lower the entry barrier for users. Q: Does the enterprise version run in production? Is the open‑source version just a toy? A: The platform is production‑ready; the public cloud version has run for over 700 days with a 99.999% SLA, and the open‑source core code matches the enterprise edition.

Installation Prerequisites

CentOS 7 (systemd) is recommended; Debian is possible but not covered.

Sufficient hardware resources; a cluster is advised for real use.

Network Time Protocol (NTP) synchronization.

Static IP configuration on all servers.

Clean environment – remove any existing Docker or kubelet installations.

Avoid changing the hostname after installation (or update /etc/host and /etc/hostname accordingly).

Installation Commands

One‑click installation (if the environment meets the requirements):

bash<(curl -s http://repo.goodrain.com/install/3.5/start.sh)

For adding a compute node (run on the manager node):

grctl node add -i <compute_node_ip> --role compute

uuid=$(grctl node list | grep <compute_node_ip> | awk '{print $2}')

grctl install compute --nodes $uuid

grctl node up $uuid

After installation, access the UI at http:// :7070/ , register the first user as the administrator, and explore the dashboard.

Performance Tuning & Optimization

1. Increase file descriptor limits:

vi /etc/security/limits.conf

# add the following lines
root soft nofile 2400
root hard nofile 102400
* soft nofile 102400
* hard nofile 102400

2. Kernel parameter adjustments (add to /etc/sysctl.conf and apply with sysctl -p ):

net.ipv4.neigh.default.gc_stale_time=120
net.ipv4.conf.all.rp_filter=0
net.ipv4.conf.default.rp_filter=0
net.ipv4.conf.default.arp_announce=2
net.ipv4.conf.all.arp_announce=2
net.ipv4.tcp_max_tw_buckets=5000
net.ipv4.tcp_syncookies=1
net.ipv4.tcp_max_syn_backlog=1024
net.ipv4.tcp_synack_retries=2
net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=1
net.ipv4.conf.lo.arp_announce=2
vm.swappiness=10
vm.vfs_cache_pressure=50
vm.overcommit_memory=1
net.core.somaxconn=65535
net.netfilter.nf_conntrack_max=655350
net.netfilter.nf_conntrack_tcp_timeout_established=1200

3. Increase NFS mount concurrency:

vi /etc/sysctl.conf

# add the following line
sunrpc.tcp_slot_table_entries=28

4. Enable container swap limit (if the kernel does not support it by default):

echo 'GRUB_CMDLINE_LINUX="cgroup_enable=memory swapaccount=1"' >> /etc/default/grub

grub2-mkconfig -o /boot/grub2/grub.cfg

After applying the above settings, restart the system to make them effective.

For more detailed information, refer to the official documentation links provided in the article.