home/blog/2025-04-23-hertzbeat-upgrade-guide-from-v1.6.1-to-v1.7.0-helm-mode.md
Ensure the following tools are installed:
Verify current deployment information:
helm list -n <your-namespace>
# If the old chart package is missing, export values.yaml with:
helm get values hertzbeat -n <your-namespace> > hertzbeat-1.6.1-values.yaml
Data Backup:
For custom monitoring templates:
Backup
/opt/hertzbeat/definefrom the running pod:bashkubectl cp hertzbeat/hertzbeat-978477f84-fr894:/opt/hertzbeat/define ./defineFor external databases (MySQL/PostgreSQL):
Use
mysqldump/pg_dumpor copy PVC directories:bashkubectl get pvc -n hertzbeat
helm repo update
helm pull hertzbeat/hertzbeat --version 1.7.0 --untar
cd hertzbeat
Or clone from GitHub:
git clone https://github.com/hertzbeat/helm-charts.git
cd helm-charts/charts/hertzbeat
Compare and merge configurations:
diff -u ../hertzbeat-1.6.1-values.yaml values.yaml
# Use vimdiff to compare and merge changes
Key configurations to check:
image.tagresourcespersistenceservice.typehelm upgrade hertzbeat . -n <your-namespace> \
--values values.yaml \
--dry-run \
--debug
helm upgrade hertzbeat . -n <your-namespace> \
--values values.yaml \
--atomic \ # Auto-rollback on failure
--timeout 10m # Set timeout
helm status hertzbeat -n <your-namespace>
kubectl get pods -n <your-namespace> -l app.kubernetes.io/instance=hertzbeat
kubectl logs -n <your-namespace> -l app.kubernetes.io/instance=hertzbeat --tail=100