Offline Upgrade Cloud Edge Collaboration Module¶
This page explains how to install or upgrade after downloading the Cloud Edge Collaboration Module.
Info
The kant mentioned in the following commands or scripts is the internal development code name of the Cloud Edge Collaboration Module.
Load Images from the Downloaded Installation Package¶
You can load images in one of the following two ways. When there is an image repository in the environment, it is recommended to choose the chart-syncer to synchronize the images to the image repository for more efficient and convenient installation.
Use chart-syncer to Synchronize Images¶
Using chart-syncer allows you to upload the Chart and its dependent image packages from the downloaded installation package to the image repository and Helm repository used when deploying DCE with the installer.
First, find a node that can connect to the image repository and Helm repository (such as a fire node), create a load-image.yaml configuration file on the node, and fill in the configuration information such as the image repository and Helm repository.
-
Create load-image.yaml
Note
All parameters in this YAML file are required.
If a chart repo is already installed in the current environment, chart-syncer also supports exporting the chart to a tgz file.
load-image.yamlsource: intermediateBundlesPath: kant # Path to run the load-image.yaml file on the node. target: containerRegistry: 10.16.10.111 # Image repository address containerRepository: release.daocloud.io/kant # Image repository path repo: kind: HARBOR # Type of Helm Chart repository url: http://10.16.10.111/chartrepo/release.daocloud.io # Helm repository address auth: username: "admin" # Image repository username password: "Harbor12345" # Image repository password containers: auth: username: "admin" # Helm repository username password: "Harbor12345" # Helm repository password
If a helm repo is not added on the current node, chart-syncer also supports exporting the chart to a tgz file and storing it in a specified path.
load-image.yamlsource: intermediateBundlesPath: kant # Path to run the load-image.yaml file on the node. target: containerRegistry: 10.16.10.111 # Image repository url containerRepository: release.daocloud.io/kant # Image repository path repo: kind: LOCAL path: ./local-repo # Local path of the chart containers: auth: username: "admin" # Image repository username password: "Harbor12345" # Image repository password
-
Run the command to synchronize images.
Load Images Using Docker or containerd¶
Unpack and load the image files.
-
Unpack the tar compressed file.
After successful unpacking, you will get 3 files:
- hints.yaml
- images.tar
- original-chart
-
Load the images from the local 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 keep the Registry, Repository consistent with the installation.
Upgrade¶
There are two ways to upgrade. You can choose the corresponding upgrade solution based on the prerequisite operations:
-
Check if the Cloud Edge Collaboration Helm repository exists.
If the result is empty or shows as below, proceed to the next step; otherwise, skip the next step.
-
Add the Helm repository for Cloud Edge Collaboration.
-
Update the Helm repository for Cloud Edge Collaboration.
-
Choose the Cloud Edge Collaboration version you want to install (it is recommended to install the latest version).
The output will be similar to:
-
Backup the
--set
parameters.Before upgrading the Cloud Edge Collaboration version, it is recommended to run the following command to back up the
--set
parameters of the old version. -
Update kant crds.
-
Run
helm upgrade
.Before upgrading, it is recommended to modify the global.imageRegistry field in bak.yaml to the current image repository address.
-
Backup the
--set
parameters.Before upgrading the Cloud Edge Collaboration version, it is recommended to run the following command to back up the
--set
parameters of the old version. -
Update kant crds.
-
Run
helm upgrade
.Before upgrading, it is recommended to modify the global.imageRegistry field in bak.yaml to the current image repository address.