v6.1.1-release

Fix Bugs

• Fixed the issue where the role information was empty when adding a new node.
• Fixed the issue where node information was not cleared after deleting a cluster.
• Fixed the issue where service resources were not deleted after a component build was abandoned.
• Fixed the issue where gateway records were not deleted when a component port was removed.
• Fixed incorrect storage statistics in the team application list.
• Fixed the issue where refreshing the application list resulted in an empty page.
• Fixed the issue where the pipeline plugin did not have an entry displayed.
• Fixed the issue where configuration files shared with other components were incorrectly displayed in shared storage.
• Fixed the issue where rbd-db failed to start during K3S installation.
• Fixed the inability to manually add custom TCP routes.
• Fixed the issue where external port routes for TCP components were not deleted.
• Fixed the error when adding a certificate with the name *.
• Fixed the issue where Java Maven multi-module source build parameters could not be saved correctly.
• Fixed the scrolling behavior at the bottom of the Web terminal.
• Fixed the error when switching the build source of a component to image-based builds.
• Added validation rules for HTTP routes in gateway management to disallow purely numeric entries.
• Fixed the issue where selecting a component without ports caused abnormal refreshing when adding routes in the gateway.

What's Changed

• perf: support over score by @ZhangSetSail in #2118
• fix: add log show node by @ZhangSetSail in #2123
• fix: sort node role by @ZhangSetSail in #2124
• fix: delete svc failure by @ZhangSetSail in #2125
• fix: create route failure by @ZhangSetSail in #2126
• perf: add log by @ZhangSetSail in #2127
• fix: delete mb service failure by @ZhangSetSail in #2128
• perf: show code 500 err by @ZhangSetSail in #2129
• fix: delete outer tcp port svc failure by @ZhangSetSail in #2130

Full Changelog: v6.1.0-release...v6.1.1-release

Upgrade

• For online environments, perform the upgrade in Platform Management > Enterprise Settings > Upgrade.
• For offline environments, refer to the upgrade documentation: https://www.rainbond.com/docs/upgrade/latest-version.

v6.1.0-release

Rainbond v6.1 Released: The Final Version of 2024, Production-Ready with Enhanced User Experience

As 2024 comes to a close, we proudly announce the release of Rainbond v6.1, marking a perfect conclusion to the year. As the last release of Rainbond in 2024, v6.1 signifies that the Rainbond v6 series has officially entered the production-ready stage. This not only indicates that the platform is fully equipped for production environments but also represents significant advancements in stability, performance optimization, and user experience.

The core highlight of v6.1 is the newly designed team space view, focusing on user experience. With a clearer interface and smoother workflows, users can manage teams, create applications, and configure resources more efficiently, embodying the user-centric design philosophy.

Team Dashboard Page

We have redesigned the Team Dashboard page, removing unnecessary sidebars and related guidance content. The layout has been optimized to focus on applications, providing users with a simpler and more efficient operation experience.

New Personal Center

We have transformed the previously globally shared image repositories and Git repositories into individual user configurations. Each user's resources are now exclusive to them, enhancing the flexibility and privacy of resource management.

All-New Image Repository

The all-new image repository integration supports seamless connections with Docker Registry and Harbor repositories. Once integrated, users can directly search for images and their tags on the Rainbond platform and quickly create components, significantly improving image management and component construction efficiency.

File Management

A new file management feature has been added, supporting file uploads and downloads, as well as creating and uploading folders. This greatly enhances the flexibility and convenience of file operations.

Detailed Changes

• Added file management functionality
• Gateway now supports adding domain multi-paths
• Cert Manager supports automatic certificate issuance
• Redesigned Team Dashboard page with card and list view toggles
• Added Docker image repository integration functionality
• Adjusted Git and image repository authentication to user granularity
• Fixed an issue with quick installation binding to IPv6 addresses
• Fixed an issue where gateway target services could not be added
• Fixed permission issues for regular users creating components
• Fixed an issue where deleting ports in components did not remove related routes in gateway management
• Fixed an issue where the default cluster could not be deleted after console migration

v6.0.3-release

What's Changed

Bug Fixes

• Fixed an issue where component logs could not be paused, log retrieval was ineffective, and the most recent 1000 logs were empty.
• Fixed incorrect data statistics in component resource monitoring.
• Fixed an issue where the rbd-hub multi-replica setup failed to push images.
• Fixed an issue where applications installed from the local component library with TCP ports failed to make the TCP ports accessible after installation.
• Fixed an issue where deleting an application did not remove gateway HTTP and TCP policies.
• Fixed an issue where newly added TCP routes under a team were not visible under the application.
• Fixed an issue where the SSH protocol repository could not load SSH keys.
• Optimized gateway management by setting the HTTP policy's target service to the component name.
• Optimized gateway management to support domain name search in HTTP policies.
• Fixed an issue where installing old-version plugins caused the page to fail to load.
• Fixed incorrect display of component statuses in cluster management.
• Fixed an issue where incorrect UI validation rules in platform-managed image repositories prevented access to private repositories.
• Fixed an issue where local storage node affinity settings were not applied.

Upgrade

For online upgrades, navigate to Platform Management -> Enterprise Settings -> Version Upgrade.
For offline upgrades, refer to the documentation: offline upgrade.

Notes

If you are upgrading from v6.0.2 to v6.0.3 and are using components with local storage, the local storage node affinity issue will affect dependencies. To resolve this issue, you will need to back up your data and recreate the affected components.

v6.0.2-release

Bug Fixes

• Fixed the issue where MinIO's newer versions do not support older CPU architectures.
• Fixed the inability to save edited gateway paths.
• Fixed the error when connecting the gateway to a component in the topology editor.
• Added textual descriptions for host installation.
• Fixed incorrect display of component status in cluster management.
• Fixed the issue where deleting the last registered node did not re-sync the server.
• Fixed errors during the installation of some applications in the open-source application store, including initialization wait time.

v6.0.1-release

Bug Fixes

• Support for deleting registered nodes during host installation
• Missing default HTTP domain name for host cluster integration
• Alibaba Cloud Linux 3.2 ARM64 quick installation fails to start
• Console migration fails to start
• Modify internal component repository form validation rules
• Unable to integrate with K8s clusters
• Fix logic error in quick installation script
• Plugin installation causes Sqlite lock
• Offline import of application record ID does not auto-increment

v6.0.0-release

What's Changed

• Refactored the host installation process and upgraded the default K8s version to 1.30.
• Added support for online platform upgrades through the UI.
• Unified and upgraded the platform UI interface styles and designs.
• Enhanced the platform-level plugin extension framework.
• Supported source code builds with the option to select the build language (e.g., Dockerfile or source code). #1426
• Removed the strong dependency on shared storage; switched to S3 for storing certain shared files.
• Replaced the underlying gateway implementation with Apisix to improve gateway stability and support various plugins.
• Simplified core components by removing the node module and merging eventlog and webcli modules.
• Eliminated the dependency on etcd for core components.
• Optimized API response speeds.
• Enhanced high-concurrency performance.
• Removed the ServiceMesh governance model.
• Replaced the monitoring module with the official Prometheus image, supporting rule definitions via configuration files.
• Fixed the issue where default component-injected variables started with _, avoiding conflicts. #1719

v5.17.3-release

What's Changed

Feature Optimize

• add new nodes does not take effect.
• k8s resource creation failed in HELM creation component part. #1958
• multi-architecture cluster fails to export helm chart package. #1955
• fixed the problem of incorrect display of team list view
• remove redundant display from team list view
• add indexes to some tables to optimize query speed

v5.17.2-release

What's Changed

Feature Optimize

• every time a published application is deployed or upgraded, the shared storage will disappear #1724
• component builds Openapi interface and calls exception. #1874
• when a team is bound to multiple clusters, multiple teams will be displayed. #1827
• nginx ssl_ciphers loopholes
• helm application installation failed #1777
• error reported when modifying plug-in configuration group #1934
• harbor warehouse webhook error
• default gateway display page modification
• support global private image warehouse configuration

v5.17.1-release

What's Changed

Feature Optimize

• Host-based installation Allows you to customize Rainbond cluster installation parameters using a forms
• Optimizes Helm installation with support for customizing Helm installation parameters through forms
• Optimize the NodeJS front-end project build cache strategy to speed up build

v5.17.0-release

New Features:

• Optimized API service dependencies to ensure limited service availability even when dependencies fail to start properly #1820
• Added support for configuring private image repository credentials, addressing deployment issues when starting from an image #1821

Feature Enhancements:

• Added support for hostAliases in components. #1812
• Display of component-mounted storage whether it should show the physical machine's directory (prompt in the product, link to the documentation).
• Template publishing needs to support searching. #1843
• Shared configuration files need a search/filter box. #1835
• Support for showing which components depend on a component when there are dozens of components depending on the same component. #1836
• When selecting components in bulk (10 components per page), the order changes when the component state changes, causing selected components to switch to others. #1844
• Added entry to the team wizard page for creating a new team. #1850
• Support for pre-checking whether shared configuration files are depended upon by other components. #1837
• Support for forcefully deleting mounted configuration files, filtering by application, component, and configuration file name. #1838
• Added pod affinity for build tasks #1842
• Trigger keywords for automatic builds should be configurable, and build triggers should notify WeChat Work or DingTalk. #1770
• Offline imported or team-released application templates should be visible in other teams. No isolation of permissions between teams. #1825

Bug Fixes:

• First-time building of the runner image fails to pull. (Cannot reproduce)
• Components created with OAuth, after quick duplication, require re-editing of OAuth build sources. (Cannot reproduce)
• Export failure of Helm chart package, there is an issue.
• Gateway parameter configuration error causing startup failure. #1840
• Outer close button for OAuth settings does not work. #1841
• Advanced properties of components, health checks do not take effect. #1809
• Dockerfile build args parameter does not take effect. #1685
• Unable to save GOPRIVATE during Golang repository build. #1794