Offline Upgrade of Middleware - ElasticSearch Module¶
This page explains how to install or upgrade the ElasticSearch module of the Middleware after downloading it from the Download Center.
Info
The term mcamel used in the following commands or scripts is the internal development code name for the Middleware module.
Loading Images from Installation Package¶
You can load the images using one of the following two methods. It is recommended to use chart-syncer to sync the images to your container registry when there is an container registry available, as it is more efficient and convenient.
Syncing Images to Container Registry Using chart-syncer¶
-
Create load-image.yaml file.
Note
All the parameters in this YAML file are mandatory. You need to have a private container registry and modify the relevant configurations.
If you have already installed a chart repo in your environment, chart-syncer also supports exporting a chart as a tgz file.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # The relative path to where the charts-syncer command will be executed, 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 type url: http://10.16.10.111/chartrepo/release.daocloud.io # Change it to your 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 you haven't installed a chart repo in your environment, chart-syncer also supports exporting a chart as a tgz file and storing it in the specified path.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # The relative path to where the charts-syncer command will be executed, 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 to the chart containers: auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password
-
Run the command to sync the images.
Directly Loading with Docker or containerd¶
Extract and load the image files.
-
Extract the tar archive.
tar -xvf mcamel-elasticsearch_0.10.1_amd64.tar cd mcamel-elasticsearch_0.10.1_amd64 tar -xvf mcamel-elasticsearch_0.10.1.bundle.tar
After successful extraction, you will have three files:
- hints.yaml
- images.tar
- original-chart
-
Load the images from the local directory to Docker or containerd.
Note
Each node needs to perform the Docker or containerd image loading operation. After loading is complete, tag the images to match the Registry and Repository used during installation.
Upgrade¶
There are two methods to upgrade. Choose the corresponding upgrade method based on the pre-operation you performed:
-
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 (it is recommended to install the latest version).
-
Back up the
--set
parameters.Before upgrading to a new 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-elasticsearch.yaml with the URL of the container registry you are currently using.
-
Back up the
--set
parameters.Before upgrading to a new 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-elasticsearch.yaml with the URL of the container registry you are currently using.