Update Content

Adjust version or components according to specific upgrade content. For example:

• Update FinClip to specified version
• Update specific components to latest version

---

File Preparation

1. Download and upload offline image package to deployment server Image package download link provided by FinoGeeks

2. Import offline image Use the following command to import the image and push to private registry:

   for i in `docker load -i <offline-image-package-filename> |awk '{print $NF}'` ; do docker tag $i `echo $i|awk -F '/' '{print "registry.finogeeks.internal:5000/mop/"$NF}'` ; docker push `echo $i|awk -F '/' '{print "registry.finogeeks.internal:5000/mop/"$NF}'` ;done

---

Update Steps

1. Backup Configuration File

   Backup FinClip configuration file, adjust path according to version (example path: /data/finclip-installation/1.12.0/values.yaml)

   cp /data/finclip-installation/1.12.0/values.yaml /data/finclip-installation/1.12.0/values-$(date +%Y%m%d%H%M%S).yaml

2. Modify Configuration File

   Edit FinClip configuration file:

   vim values.yaml

   Modify configuration according to upgrade requirements. For example:

   apps:
     integration_api: registry.finogeeks.internal:5000/mop/integration-api:<target-version-number>

3. Execute Upgrade Command Use helm tool to perform upgrade with the following command:

   helm upgrade finclip -n finclip /data/finclip/<version-number>

Startup Verification

1. Check Pod Status

   After upgrade is complete, confirm all components are running properly:

   kubectl get pod -n finclip

   Status column should display: Running

Important Notes

1. Offline image package links and component version numbers should be adjusted according to actual requirements.
2. Ensure the path and tag format for pushing images to private registry are correct.
3. It is recommended to backup relevant data and configuration files before upgrading for rollback purposes.
4. If issues occur, use kubectl -n finclip logs to view specific component logs for troubleshooting.