Skip to content

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 container registry in the environment, it is recommended to choose the chart-syncer to synchronize the images to the container registry 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 container registry and Helm repository used when deploying DCE with the installer.

First, find a node that can connect to the container registry 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 container registry and Helm repository.

  1. 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.yaml
    source:
  intermediateBundlesPath: kant # (1)!
target:
  containerRegistry: 10.16.10.111 # (2)!
  containerRepository: release.daocloud.io/kant # (3)!
  repo:
    kind: HARBOR # (4)!
    url: http://10.16.10.111/chartrepo/release.daocloud.io # (5)!
    auth:
      username: "admin" # (6)!
      password: "Harbor12345" # (7)!
  containers:
    auth:
      username: "admin" # (8)!
      password: "Harbor12345" # (9)!
    1. Path to run the load-image.yaml file on the node
    2. Container registry address
    3. Container registry path
    4. Type of Helm Chart repository
    5. Helm repository address
    6. Container registry username
    7. Container registry password
    8. Helm repository username
    9. 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.yaml
    source:
  intermediateBundlesPath: kant # (1)!
target:
  containerRegistry: 10.16.10.111 # (2)!
  containerRepository: release.daocloud.io/kant # (3)!
  repo:
    kind: LOCAL
    path: ./local-repo # (4)!
  containers:
    auth:
      username: "admin" # (5)!
      password: "Harbor12345" # (6)!
    1. Path to run the load-image.yaml file on the node
    2. Container registry url
    3. Container registry path
    4. Local path of the chart
    5. Container registry username
    6. Container registry password

  2. Run the command to synchronize images.

    charts-syncer sync --config load-image.yaml

Load Images Using Docker or containerd

Unpack and load the image files.

  1. Unpack the tar compressed file.

    tar xvf kant.bundle.tar

    After successful unpacking, you will get 3 files:

    • hints.yaml
    • images.tar
    • original-chart

  2. Load the images from the local to Docker or containerd.

    docker load -i images.tar

    ctr -n k8s.io image import images.tar

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:

  1. Check if the Cloud Edge Collaboration Helm repository exists.

    helm repo list | grep kant-release

    If the result is empty or shows as below, proceed to the next step; otherwise, skip the next step.

    Error: no repositories to show

  2. Add the Helm repository for Cloud Edge Collaboration.

    helm repo add kant-release http://{harbor url}/chartrepo/{project}

  3. Update the Helm repository for Cloud Edge Collaboration.

    helm repo update kant-release

  4. Choose the Cloud Edge Collaboration version you want to install (it is recommended to install the latest version).

    helm search repo kant-release/kant --versions

    The output will be similar to:

    NAME                   CHART VERSION  APP VERSION  DESCRIPTION
kant-release/kant  0.5.0          v0.5.0       A Helm chart for kant
...

  5. 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.

    helm get values kant -n kant-system -o yaml > bak.yaml

  6. Update kant crds.

    helm pull kant-release/kant --version 0.5.0 && tar -zxf kant-0.5.0.tgz
kubectl apply -f kant/crds

  7. Run helm upgrade.

    Before upgrading, it is recommended to modify the global.imageRegistry field in bak.yaml to the current container registry address.

    export imageRegistry={your-registry}

    helm upgrade kant-release kant-release/kant \
  -n kant-system \
  -f ./bak.yaml \
  --set global.imageRegistry=$imageRegistry \
  --version 0.5.0

  1. 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.

    helm get values kant -n kant-system -o yaml > bak.yaml

  2. Update kant crds.

    kubectl apply -f ./crds

  3. Run helm upgrade.

    Before upgrading, it is recommended to modify the global.imageRegistry field in bak.yaml to the current container registry address.

    export imageRegistry={your-registry}

    helm upgrade kant-release . \
  -n kant-system \
  -f ./bak.yaml \
  --set global.imageRegistry=$imageRegistry

Comments