Offline Upgrade Middleware - RabbitMQ Module¶
This page explains how to install or upgrade the Middleware - RabbitMQ module after downloading it from the Download Center.
Info
The term mcamel mentioned in the following commands or scripts is the internal development code name of the middleware module.
Load Images from Installation Package¶
You can load the images in one of the following two ways. When an container registry exists in the environment, it is recommended to choose the chart-syncer to synchronize images to the container registry as it is more efficient and convenient.
Synchronize Images to Container Registry Using chart-syncer¶
-
Create load-image.yaml .
Note
All parameters in this YAML file are required. You need a private container registry and modify the relevant configuration.
If the current environment has installed a chart repo, chart-syncer also supports exporting the chart as a tgz file.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # This is the relative path to execute the charts-syncer command, not the relative path between this YAML file and the offline package. target: containerRegistry: 10.16.10.111 # Change it to your container registry URL containerRepository: release.daocloud.io/mcamel # Change it to your container registry repo: kind: HARBOR # It can also be any other supported Helm Chart repository category url: http://10.16.10.111/chartrepo/release.daocloud.io # Change it to the chart repo URL auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password containers: auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password
If the current environment has not installed a chart repo, chart-syncer also supports exporting the chart as a tgz file and storing it in the specified path.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # This is the relative path to execute the charts-syncer command, not the relative path between this YAML file and the offline package. target: containerRegistry: 10.16.10.111 # Change it to your container registry URL containerRepository: release.daocloud.io/mcamel # Change it to your container registry repo: kind: LOCAL path: ./local-repo # Local path of the chart containers: auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password
-
Run the command to synchronize images.
Load Directly from Docker or containerd¶
Unpack and load the image files.
-
Extract the tar archive.
tar -xvf mcamel-rabbitmq_0.13.1_amd64.tar cd mcamel-rabbitmq_0.13.1_amd64 tar -xvf mcamel-rabbitmq_0.13.1.bundle.tar
After successful extraction, you will have 3 files:
- hints.yaml
- images.tar
- original-chart
-
Load the images from the local directory to Docker or containerd.
Note
Each node needs to perform Docker or containerd image loading operations. After loading is complete, tag the images to keep the Registry and Repository consistent with the installation.
Upgrade¶
There are two ways to upgrade. You can choose the corresponding upgrade method according to the pre-operation:
-
Check if the helm repository exists.
If the result is empty or shows the following prompt, proceed to the next step; otherwise, skip the next step.
-
Add the helm repository.
-
Update the helm repository.
-
Choose the version you want to install (recommended to install the latest version).
-
Back up the
--set
parameters.Before upgrading the version, it is recommended to execute the following command to back up the
--set
parameters of the old version. -
Run
helm upgrade
.Before upgrading, it is recommended to replace the
global.imageRegistry
field in mcamel-rabbitmq.yaml with the URL of the container registry you are currently using.
-
Back up the
--set
parameters.Before upgrading the version, it is recommended to execute the following command to back up the
--set
parameters of the old version. -
Run
helm upgrade
.Before upgrading, it is recommended to replace the
global.imageRegistry
field in mcamel-rabbitmq.yaml with the URL of the container registry you are currently using.