Version Upgrade via k8s Method

1. Obtain the k8s yaml deployment files for the upgraded version. Configuration files can be referenced from Pre-Deployment Preparation.
2. Obtain the new version service images, import them into the k8s cluster or add them to the internal private server, etc., to ensure that the k8s cluster can obtain the image information.
3. In the k8s environment, data backup operations are not performed by default during the upgrade process. You can perform data backup operations as needed k8s Environment Backup and Restore.
4. Compare the component dependencies in the installed version with those in the version to be upgraded.
   • If the component dependencies are the same, update the image version information in the hengshi.yaml configuration file.

   ## Execute the following deployment command to complete the upgrade
   kubectl -n hengshi apply -f hengshi.yaml

   • If the component dependencies are different, for example, upgrading from 4.0 to 4.2, new components such as redis and flink are added, and you need to update the image and pvc related configuration information in hengshi.yaml, redis.yaml, and flink.yaml.

   ## Execute the following deployment command to complete the upgrade
   kubectl -n hengshi apply -f configmap.yaml
   kubectl -n hengshi apply -f service.yaml
   kubectl -n hengshi apply -f redis.yaml
   kubectl -n hengshi apply -f flink.yaml
   kubectl -n hengshi apply -f hengshi.yaml

   • If the component dependencies are the same, but there are known component function optimizations in the upgrade version, contact the technical staff to determine the components that need to be updated. For example, for metadb component function optimization, update the image information in the hengshi.yaml and metadb.yaml configuration files.

   ## Execute the following deployment command to complete the upgrade
   kubectl -n hengshi apply -f metadb.yaml
   kubectl -n hengshi apply -f hengshi.yaml

5. Check the startup status of all component pods. If the STATUS is all Running, the service has started successfully.
6. The upgrade is complete. Access the service address via a browser to use the HENGSHI SENSE service.
7. Notes:
   1. The flink component in version 5.1.x has been removed and does not need to be run. After the upgrade, you can consider stopping and cleaning up the flink containers.