Skip to main content

5.7.0 upgrade to 5.7.1 documentation

version change​

5.7.1 Version Changes

Console upgrade​

  1. Upgrade console
  • if the console is allinone started, execute the following operations
docker stop rainbond-allinone && docker rm rainbond-allinone
#The command parameters need to be the same as the rainbond-allinone container that was started before
docker run -d -p 7070:7070 -v ~/.ssh:/root/.ssh -v ~/rainbonddata:/app/data \
--name=rainbond-allinone --restart=always \
registry.cn -hangzhou.aliyuncs.com/goodrain/rainbond:v5.7.1-release-allinone

If the console is installed through the app market, enter the console application and choose to upgrade to version 5.7.1

Data Center Upgrade​

warning

If an external database is specified or other parameters are used when helm deploys Rainbond.Then, when executing the following upgrade command, you also need to set the previous parameters through --set.Otherwise the previous configuration will be overwritten.

Another way is to use the grctl command to upgrade.Upgrading with the grctl command avoids this problem.grctl command version is at least v5.8.0-release

  • data center side upgrade

  • update mirror source

helm upgrade --set Component.rbd_app_ui.image=registry.cn-hangzhou.aliyuncs. com/goodrain/rainbond:v5.7.1-release-allinone --set operator.image.tag=v5.7.1-release --set Cluster.installVersion=v5.7.1-release rainbond rainbond/rainbond-cluster -n rbd-system

  • Confirm pod update status

  • Confirm rolling update of all pods, about 3 minutes depending on the network

kubectl get po -n rbd-system