Offline Upgrade - Postgresql Module¶
This page explains how to install or upgrade the middleware - Postgresql module 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.
Load Images from Installation Package¶
You can load the images using either of the two methods described below. It is recommended to choose the chart-syncer method if there is an container registry available in your environment, as it is more efficient and convenient.
Sync Images to Container Registry using chart-syncer¶
-
Create load-image.yaml .
Note
All parameters in this YAML file are mandatory. You need to have a private container registry and modify the relevant configuration.
If you have an installed chart repo in the current environment, chart-syncer also supports exporting charts as tgz files.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # the relative path to where you execute the __charts-syncer__ command, not the relative path between this YAML file and the offline package target: containerRegistry: 10.16.10.111 # replace with your container registry url containerRepository: release.daocloud.io/mcamel # replace with your container registry repo: kind: HARBOR # or any other supported Helm Chart repository type url: http://10.16.10.111/chartrepo/release.daocloud.io # replace with 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 don't have an installed chart repo in the current environment, chart-syncer also supports exporting charts as tgz files and storing them in the specified path.
load-image.yamlsource: intermediateBundlesPath: mcamel-offline # the relative path to where you execute the __charts-syncer__ command, not the relative path between this YAML file and the offline package target: containerRegistry: 10.16.10.111 # replace with your container registry url containerRepository: release.daocloud.io/mcamel # replace with 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.
Load Directly from Docker or containerd¶
Extract and load the image files.
-
Extract the tar archive.
tar -xvf mcamel-postgresql_0.5.1_amd64.tar cd mcamel-postgresql_0.5.1_amd64 tar -xvf mcamel-postgresql_0.5.1.bundle.tar
After successful extraction, you will have three files:
- hints.yaml
- images.tar
- original-chart
-
Load the images to Docker or containerd from the local directory.
Note
Docker or containerd image loading operations need to be performed on each node. After loading is complete, tag the images to maintain consistency with the Registry and Repository used during installation.
Upgrade¶
There are two ways to upgrade. You can choose the corresponding upgrade method based on the prerequisite operations:
-
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.
-
Select the version you want to install (we recommend installing 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-postgresql.yaml with the address 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-postgresql.yaml with the address of the container registry you are currently using.