Releases: goodrain/rainbond
v6.3.0-release
Rainbond v6.3.0 Released | Integration of Application and Component Views for a Smooth Experience
For a long time, many users have feedback on the issue of multiple view hierarchies when using Rainbond. The multi-level hierarchy of team views, application views, component views, etc., brings certain complexity in actual operations. As a platform focused on being application-centric, this operation path has a certain gap with the positioning of "application-centric". Users need to switch between different views to complete operations from the overall application architecture to component detail configuration, which to a certain extent affects the use efficiency and the coherence of the experience.
This time, we have connected applications and components
In Rainbond v6.3.0, the application management experience has ushered in a breakthrough innovation. When you click on any component in the topology diagram in the application view, the detailed information and operation panel of that component will pop up on the right side without page jumping. All the original separate component view pages are centralized in this interface, completely saying goodbye to the tediousness of switching back and forth between application and component views. It truly achieves a smooth experience of "click where you get what you need", making application management simple and direct, greatly improving operation efficiency, and bringing you unprecedented convenience and efficiency.
See the interaction effect through the Gif diagram.
Other Changes
- Integration of application and component views
- Fixed the issue of multiple metrics appearing in component resource monitoring
- Changed the user creation logic, no longer automatically creating the affiliated team
- Fixed the failure of Gitee code pulling
- Changed the gateway to not listen on ipv6 by default #2218
- Fixed some bugs after the integration of component views
- Fixed some bugs after the integration of application views
Upgrade
- For online environments, perform the upgrade in
Platform Management > Enterprise Settings > Upgrade. - For offline environments, refer to the upgrade documentation.
Full Changelog: v6.2.1-release...v6.3.0-release
v6.2.1-release
What's Changed
Bug Fixes
- Fix incomplete export of application templates
- Fix gateway inaccessibility after restarting components post-shutdown
- Fix rbd-worker service restarts caused by probe failures #2205
- Fix inability to start components when K8S resource CPU/memory parameters are unspecified
- Fix page loading failure when team has no associated cluster after cluster deletion
- Change component CPU resource monitoring to track actual usage
Upgrade
- For online environments, perform the upgrade in
Platform Management > Enterprise Settings > Upgrade. - For offline environments, refer to the upgrade documentation.
Full Changelog: v6.2.0-release...v6.2.1-release
v6.2.0-release
What's Changed
New Features
- Pages now support automatic certificate issuance via CertManager
- Added
redirect,real-ip,proxy-rewrite, andcorsplugins to the gateway - Gateway now supports timeout configuration
Feature Enhancements and Bug Fixes
- Fix gateway could not Reload automatically
- Improved health probes for cluster components (e.g.,
rbd-api,rbd-app-ui) - Adjusted log levels for the console and cluster
- Optimized the cluster command-line tool
- Enhanced software package upload and build logic
- Improved file management functionality
- Fixed permission issues preventing regular users from exporting templates
- Resolved a bug where invited team members lacked application deployment permissions
Upgrade
- For online environments, perform the upgrade in
Platform Management > Enterprise Settings > Upgrade. - For offline environments, refer to the upgrade documentation.
Full Changelog: v6.1.3-release...v6.2.0-release
v6.1.3-release
What's Changed
Bug Fixes
- Fixed an issue where shared storage from other components was not displayed in component sharing. #2160
- Fixed the inability to save gateway routes containing uppercase/lowercase and special characters when adding them. #2154
- Added domain name validation rules for gateway additions.
- Fixed an issue with pagination display in certificate management.
- Fixed issues related to Helm.
- Fixed a memory leak in
rbd-api.
Upgrade
- For online environments, perform the upgrade in
Platform Management > Enterprise Settings > Upgrade. - For offline environments, refer to the upgrade documentation.
Full Changelog: v6.1.2-release...v6.1.3-release
v6.1.2-release
What's Changed
Bug Fixes
- Registry Storage Optimization: Changed default Registry storage backend from Minio to local-path storage
- Fixed Registry garbage collection issues
- Resolved large image build limitation: Now supports building images larger than 3GB (#2139)
- Fixed external database configuration issue in host installation mode (#2138)
- Optimized large-scale application template import: Resolved import failures for large templates (#2140)
- Fixed permission issues when installing applications from the platform management app store
- Resolved component startup issues caused by circular dependencies
Feature Improvements
- Adjusted Ingress default listening port to 7080
- Enhanced cluster connection experience with improved error messages during host cluster integration
- Removed TCP route port range restrictions, now automatically obtains port range from underlying configuration
- Improved startup log messages for component dependencies
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.
Switching Default Registry Storage
Due to various issues with the default registry connected to Minio, and the discovery that image garbage collection (GC) cannot be performed in registry v2, we are switching to local storage.
- Update the
rainbond-operatorimage to versionv6.1.2-release
Caution
Please note that after upgrading rainbond-operator, rbd-gateway will restart, which may temporarily affect your services.
$ kubectl edit deploy rainbond-operator -n rbd-system
...
spec:
...
image: registry.cn-hangzhou.aliyuncs.com/goodrain/rainbond-operator:v6.1.2-releaseTip
If you don't need the old image data, you can skip the following steps.
- Get the local path of the automatically created
rbd-hubPV
$ kubectl get pv | grep "rbd-system/rbd-hub" | awk '{print $1}' | xargs kubectl get pv -o yaml
apiVersion: v1
kind: PersistentVolume
...
spec:
...
hostPath:
path: /opt/rainbond/local-path-provisioner/pvc-926fab85-d8c1-4699-aab0-4e45c610997b_rbd-system_rbd-hub
type: DirectoryOrCreate
...
- key: kubernetes.io/hostname
operator: In
values:
- 172.17.1.23
...- Install Minio Client tool (Mc)
curl https://dl.minio.org.cn/client/mc/release/linux-amd64/mc -o /bin/mc && chmod +x /bin/mc- Get Minio Service IP
kubectl get svc -n rbd-system | grep minio-service- Copy data from Minio to local storage (execute on node
172.17.1.23)
mc alias set myminio http://10.43.61.29:9000 admin admin1234
mc mirror myminio/rbd-hub \
/opt/rainbond/local-path-provisioner/pvc-926fab85-d8c1-4699-aab0-4e45c610997b_rbd-system_rbd-hub- Clean up image data in MinIO
mc rm myminio/rbd-hubFull Changelog: v6.1.1-release...v6.1.2-release
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.
Contributors
Assets 2
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