A development team may want to build and deploy applications without assembling every Kubernetes object and delivery integration itself. Rainbond provides an application-oriented platform that brings together those workflows and the infrastructure services behind them. It can be installed into an existing Kubernetes environment, but adopting it also introduces ownership decisions around builds, images, ingress and storage. Evaluate it as a platform for a team’s applications rather than as a single isolated workload that happens to use a Helm chart.
Current guidance
Current installation documentation supports deploying into an existing Kubernetes cluster through Rainbond’s own Helm repository, while a separate quick-install path starts a bundled environment. Choose the intended architecture first; a workstation demonstration is not equivalent to adopting the platform on a shared production cluster.
The Kubernetes guide includes container-runtime, port and built-in registry configuration. These are infrastructure changes, not merely namespace-local application settings. Review the current guide’s registry authentication and transport examples against your security requirements rather than copying demonstration credentials or restarting every node runtime without a plan. Clarify ownership of ingress, storage, builds and application images.
For migration from an older release, inventory platform metadata, application definitions, source integrations, registry contents, secrets and persistent data. Test building, deploying and rolling back one representative application before bringing over a whole team. Confirm a supported release-to-release procedure and restore platform state separately from workload volumes. This advisory does not claim a tested Rainbond installation or certify its older chart prerequisites.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub does not mark goodrain/rainbond archived or disabled; this does not establish active maintenance, support or compatibility. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Rainbond is an application-centric Platform as a Service, with innovative concept and complete ecological comes from continuous verification and optimization.
By integrating best practices of Kubernetes based containers management, Service Mesh microservice architecture, CI/CD and multiple data center resource management, Rainbond provides full life-cycle management of cloud native applications, connects application and infrastructure, application and application, infrastructure and infrastructure.
Choose Rainbond for the same reasons disruptive companies do: it serve as a easy-to-use cloud native application delivery platform that offers agile development, efficient operation and lean management experience.
Features
- Kubernetes scheduling system intergated
- Application-centric product definition
- As the basic system to build the cloud native datacenter
- Supports multiple microservice architecture (Spring Cloud, Dubbo and api gateway)
- Native microservice governance (service discovery, dynamic routing, limiting and fuse) based on extendable Service Mesh
- Business-level application performance analysis supports multiple types protocols (HTTP, Mysql, PostgreSQL)
- Build applications from source codeS (Java, PHP, Python, Golang, Ruby, etc.)
- Continuous build and deployment from private and public git repositories
- Quick application build with container image, docker-run command and docker-compose
- Support application group full backup and recovery, migration of application groups across tenants or across data centers.
- Pluggable data center supports various types of load balancing, SDN networks, various types of storage systems development
- Application plug-in system support, flexible extension of application ancillary functions, such as log processing, firewall, traffic analysis, etc
- Public and private application market with complete application sharing mechanism
- Multiple data center and across data center application deployment
- The management node (platform service) HA available.
- Cluster automatic operation and maintenance, monitoring multidimensional indicators.
- Provide complete business solution cloud delivery process.
Quick Start
Architecture
Historical illustration unavailable.
Roadmap
Read the Roadmap.
Sources & further reading
Spotted something that needs another look?
Help improve this page →