Offline upgrade global management module¶
This page explains how to install or upgrade the global management module after downloading it from Download Center.
Info
The word ghippo
appearing in the commands or scripts below is the internally developed code name for the global management module.
Synchronize image to the container registry¶
First, synchronize the image to the specified container registry through chart-syncer.
-
Create load-image.yaml
Note
All parameters in this YAML file are required. You need a private container registry and modify related configurations.
If the current environment has installed the chart repo, chart-syncer also supports exporting the chart as a tgz file.
source: intermediateBundlesPath: ghippo-offline # relative path to charts-syncer # But not the relative path between this YAML file and the offline package target: containerRegistry: 10.16.10.111 # need to be changed to your container registry url containerRepository: release.daocloud.io/ghippo # need to be changed to your container registry repo: kind: HARBOR # Can also be any other supported Helm Chart repository class url: http://10.16.10.111/chartrepo/release.daocloud.io # need to change to 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 chart repo is not installed in the current environment, chart-syncer also supports exporting the chart as a tgz file and storing it in the specified path.
source: intermediateBundlesPath: ghippo-offline # relative path to charts-syncer # But not the relative path between this YAML file and the offline package target: containerRegistry: 10.16.10.111 # need to be changed to your container registry url containerRepository: release.daocloud.io/ghippo # need to be changed to your container registry repo: kind: LOCAL path: ./local-repo # chart local path containers: auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password
-
Execute the synchronous image command.
Load image file¶
Unzip and load the image file.
-
Unzip the tar archive.
After successful decompression, you will get 3 files:
- hints.yaml
- images.tar
- original-chart
-
Load the image locally to Docker or containerd.
Note
After the loading is complete, the tag image is required to keep the Registry and Repository consistent with the installation.
upgrade¶
There are two ways to upgrade. You can choose the corresponding upgrade plan according to the pre-operations:
Note
When upgrading from v0.11.x (or lower) to v0.12.0 (or higher), you need to change all keycloak keys in bak.yaml
to keycloakx.
Example modification of this key:
change into:
-
Check whether the global management helm repository exists.
If the returned result is empty or as prompted, proceed to the next step; otherwise, skip the next step.
-
Add the globally managed helm repository.
-
Update the globally managed helm repository.
-
Select the version of Global Management you want to install (the latest version is recommended).
-
Back up the
--set
parameter.Before upgrading the global management version, it is recommended that you run the following command to back up the
--set
parameter of the old version. -
Execute
helm upgrade
.Before upgrading, it is recommended that you override the
global.imageRegistry
field in bak.yaml to the address of the currently used container registry.
-
Back up the
--set
parameter.Before upgrading the global management version, it is recommended that you run the following command to back up the
--set
parameter of the old version. -
Execute
helm upgrade
.Before upgrading, it is recommended that you overwrite
global.imageRegistry
in bak.yaml to the address of the current image registry.