Offline Upgrade¶
The Workbench supports offline upgrades. You need to first load the image from the installation package and then run the corresponding command to upgrade.
After unpacking, you will get a compressed bundle: amamba_x.y.z.bundle.tar
Load Image from Installation Package¶
Support loading images in two ways.
Sync Images via charts-syncer¶
If there is an container registry in the environment, it is recommended to synchronize the images to the container registry through charts-syncer for more efficient and convenient operation.
-
Create
load-image.yaml
with the following content as the configuration file for charts-syncer.All parameters in the
load-image.yaml
file are required. You need a private container registry and refer to the following instructions to modify each configuration. For detailed explanation of the charts-syncer configuration file, refer to its official documentation.If the HARBOR chart repo is already installed in the environment, charts-syncer also supports exporting the chart as a tgz file.
load-image.yamlsource: intermediateBundlesPath: amamba-offline # (1)! target: containerPrefixRegistry: 10.16.10.111 # (2)! repo: kind: HARBOR # (3)! url: http://10.16.10.111/chartrepo/release.daocloud.io # (4)! auth: username: "admin" # (5)! password: "Harbor12345" # (6)! containers: auth: username: "admin" # (7)! password: "Harbor12345" # (8)!
- Relative path to run the charts-syncer command, not the relative path between this YAML file and the offline package
- Change to your container registry url
- Can also be any other supported Helm Chart repository category
- Change to the chart repo project url
- Your container registry username
- Your container registry password
- Your container registry username
- Your container registry password
If the CHARTMUSEUM chart repo is already installed in the environment, charts-syncer also supports exporting the chart as a tgz file.
load-image.yamlsource: intermediateBundlesPath: amamba-offline # (1)! target: containerPrefixRegistry: 10.16.10.111 # (2)! repo: kind: CHARTMUSEUM # (3)! url: http://10.16.10.111 # (4)! auth: username: "rootuser" # (5)! password: "rootpass123" # (6)! containers: auth: username: "rootuser" # (7)! password: "rootpass123" # (8)!
- Relative path to run the charts-syncer command, not the relative path between this YAML file and the offline package
- Change to your container registry url
- Can also be any other supported Helm Chart repository category
- Change to chart repo url
- Your container registry username, if chartmuseum does not have login authentication enabled, you do not need to fill in auth
- Your container registry password
- Your container registry username
- Your container registry password
If the chart repo is not installed in the current environment, charts-syncer also supports exporting the chart as a
tgz
file and storing it in a specified path.source: intermediateBundlesPath: amamba-offline # (1)! target: containerRegistry: 10.16.23.145 # (2)! containerRepository: release.daocloud.io/amamba # (3)! repo: kind: LOCAL path: ./local-repo # (4)! containers: auth: username: "admin" # (5)! password: "Harbor12345" # (6)!
- Relative path to run the charts-syncer command, not the relative path between this YAML file and the offline package
- Change to your container registry url
- Change to your container registry
- Local path of the chart
- Your container registry username
- Your container registry password
-
Place amamba_x.y.z.bundle.tar in the amamba-offline folder.
-
Run the command to sync images.
Load Images Directly via Docker or containerd¶
-
Unpack the
tar
compressed bundle.After successful unpacking, you will get 3 files:
- hints.yaml
- images.tar
- original-chart
-
Run the following command to load the images from the local to Docker or containerd.
Note
- Images need to be loaded via Docker or containerd on each node.
- After loading, the images need to be tagged to match the Registry, Repository, and installation consistency.
Upgrade¶
-
Check if the Workbench helm repository exists.
If the result is empty or shows the following message, proceed to the next step; otherwise, skip the next step.
-
Add the helm repository for Workbench.
-
Update the helm repository for Workbench.
- If the Helm version is too low and the update fails, try executing helm update repo
-
Choose the version of the Workbench you want to install (recommended to install the latest version).
NAME CHART VERSION APP VERSION DESCRIPTION amamba-release/amamba 0.24.0 0.24.0 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.23.0 0.23.0 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.22.1 0.22.1 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.22.0 0.22.0 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.21.2 0.21.2 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.21.1 0.21.1 Amamba is the entrypoint to DCE5.0, provides de... amamba-release/amamba 0.21.0 0.21.0 Amamba is the entrypoint to DCE5.0, provides de... ...
-
Back up the
--set
parameters.Before upgrading the Workbench version, it is recommended to run the following command to back up the
--set
parameters of the old version. -
Run
helm upgrade
.Before upgrading, it is recommended to overwrite the
global.imageRegistry
field in bak.yaml with the current container registry address.
-
Prepare the
original-chart
(obtained by unpacking amamba_x.y.z.bundle.tar). -
Back up the
--set
parameters.Before upgrading the Workbench version, it is recommended to run the following command to back up the
--set
parameters of the old version. -
Run
helm upgrade
.Before upgrading, it is recommended to overwrite the
global.imageRegistry
field in bak.yaml with the current container registry address.