Offline upgrade observability module¶
This page explains how to install or upgrade the observability module after downloading it from Download Center.
Info
The word insight appearing in the following commands or scripts is the internal development codename of the observability module.
Decompression¶
After decompression, two bundle packages can be obtained, namely insight and insight agent.
# ll insight_v0.25.3_amd64
总用量 2899996
-rw-r--r-- 1 root root 2367463936 4月 2 18:36 insight_0.25.3.bundle.tar
-rw-r--r-- 1 root root 602125824 4月 2 18:35 insight-agent_0.25.3.bundle.tar
Load the image from the installation package¶
You can load the image in one of the following two ways. When there is a container registry in the environment, it is recommended to select chart-syncer to synchronize the image to the container registry. This method is more efficient and convenient. Please note that the version of charts-syncer should be greater than or equal to 0.0.22.
chart-syncer synchronously images to the container registry¶
-
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 HARBOR chart repo, chart-syncer also supports exporting the chart as a tgz file.
source: intermediateBundlesPath: insight-offline # The relative path to run the charts-syncer command, not the relative path between this YAML file and the offline bundle target: containerPrefixRegistry: 10.16.10.111 # need to be changed to your container registry url appendOriginRegistry: true 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 project 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 current environment has installed the CHARTMUSEUM chart repo, chart-syncer also supports exporting the chart as a tgz file.
source: intermediateBundlesPath: insight-offline # The relative path to run the charts-syncer command, not the relative path between this YAML file and the offline bundle target: containerPrefixRegistry: 10.16.10.111 # need to be changed to your container registry url appendOriginRegistry: true repo: kind: CHARTMUSEUM # Can also be any other supported Helm Chart repository class url: http://10.16.10.111 # need to change to chart repo url auth: username: "rootuser" # Your container registry username. If chartmuseum disable login verification, auth can be vacant. password: "rootpass123" # Your container registry password containers: auth: username: "rootuser" # Your container registry username password: "rootpass123" # 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: insight-offline # The relative path to run the charts-syncer command, not the relative path between this YAML file and the offline bundle target: containerPrefixRegistry: 10.16.10.111 # need to be changed to your container registry url repo: kind: LOCAL path: ./local-repo # chart local path containers: auth: username: "admin" # Your container registry username password: "Harbor12345" # Your container registry password
-
Run the synchronous imageing command.
Docker or containerd direct loading¶
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
Each node needs to perform Docker or containerd loading image operation. 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. Before upgrading, please pay attention to the "Upgrade-note"
-
Check whether the Insight helm repository exists.
If the returned result is empty or as prompted, proceed to the next step; otherwise, skip the next step.
-
Add the Insight helm repository.
-
Update the globally managed helm repository.
-
Select the version of Insight you want to install (the latest version is recommended).
-
Back up the
--set
parameter.Before upgrading the Insight version, it is recommended that you run the following command to back up the
--set
parameter of the old version. -
Run
helm upgrade
.as well as
-
Back up the
--set
parameter.Before upgrading the Insight version, it is recommended that you run the following command to back up the
--set
parameter of the old version. -
Run
helm upgrade
.Before upgrading, it is recommended that you overwrite global.imageRegistry in bak.yaml to the address of the current container registry.
helm upgrade insight . \ -n insight-system \ -f ./insight.yaml \ --set global.imageRegistry=$imageRegistry
as well as