Offline Upgrade of Cluster Inspection Module¶
This page explains how to install or upgrade the cluster inspection module after downloading it from the Download Center.
Info
The term kocllie mentioned in the following commands or scripts is the internal development codename for the cluster inspection module.
Loading Images from the Downloaded Package¶
You can load the images in one of the following two ways. If there is an image repository in your environment, it is recommended to choose chart-syncer to synchronize the images to the image repository as it is more efficient and convenient.
Option 1: Synchronize Images with chart-syncer¶
Using chart-syncer, you can upload the charts from the downloaded package along with their dependent image packages to the image repository and Helm repository used by the installer.
First, locate a node (such as a spark node) that can connect to both the image repository and the Helm repository. On this node, create a load-image.yaml configuration file and fill in the necessary information about the image repository and the Helm repository.
-
Create load-image.yaml file.
Note
All parameters in this YAML file are mandatory.
If a chart repo is already installed in the current environment, chart-syncer also supports exporting the chart as a tgz file.
load-image.yamlsource: intermediateBundlesPath: kocllie # Path where the __load-image.yaml__ file is executed on the node. target: containerRegistry: 10.16.10.111 # Image repository address containerRepository: release.daocloud.io/kocllie # Image repository path repo: kind: HARBOR # Helm Chart repository type 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 there is no helm repo added on the current node, chart-syncer also supports exporting the chart as a tgz file and storing it in the specified path.
load-image.yamlsource: intermediateBundlesPath: kocllie # Path where the __load-image.yaml__ file is executed on the node. target: containerRegistry: 10.16.10.111 # Image repository URL containerRepository: release.daocloud.io/kocllie # Image repository path repo: kind: LOCAL path: ./local-repo # Local path to the chart containers: auth: username: "admin" # Image repository username password: "Harbor12345" # Image repository password
-
Run the command to synchronize the images.
Option 2: Load Images using Docker or containerd¶
Unzip and load the image files.
-
Unzip the tar package.
After successful extraction, you will have three files:
- hints.yaml
- images.tar
- original-chart
-
Load the images from the tar file into Docker or containerd.
Note
Each node needs to perform Docker or containerd image loading operation. After the loading is complete, tag the images to match the registry and repository used during installation.
Upgrade¶
There are two upgrade methods. You can choose the corresponding upgrade approach based on the prerequisite operations:
-
Check if the cluster inspection 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 cluster inspection Helm repository.
-
Update the cluster inspection Helm repository.
-
Select the version of cluster inspection module you want to install (it is recommended to install the latest version).
-
Backup
--set
parameters.Before upgrading the cluster inspection module, it is recommended to run the following command to back up the
--set
parameters of the previous version. -
Update kocllie crds.
-
Run
helm upgrade
.Before the upgrade, it is recommended to modify the global.imageRegistry field in the bak.yaml file to the current image repository address being used.
-
Backup
--set
parameters.Before upgrading the cluster inspection module, it is recommended to run the following command to back up the
--set
parameters of the previous version. -
Update kocllie crds.
-
Run
helm upgrade
.Before the upgrade, it is recommended to modify the global.imageRegistry field in the bak.yaml file to the current image repository address being used.