Upgrade PMM Server using Helm¶
Percona releases new chart versions to update containers when:
- A new version of the main container is available
- Significant changes are made
- Critical vulnerabilities are addressed
UI Update feature disabled by default
The UI update feature is disabled by default and should remain so. Do not modify or add the following parameter in your custom values.yaml file:
pmmEnv:
DISABLE_UPDATES: "1"
Before you begin¶
Before starting the upgrade, complete these preparation steps to ensure you can recover your system if needed and confirm compatibility with the new version:
-
Create a backup before upgrading, as downgrades are not possible. Therefore, reverting to a previous version requires a backup made prior to the upgrade.
-
To reduce downtime, pre-pull the new image on the node where PMM is running:
# Replace <version> with the latest PMM version docker pull percona/pmm-server:<version>
Upgrade steps¶
Follow these steps to upgrade your PMM Server while preserving your monitoring data and settings—you can restore from your backup if needed.
-
Update Helm repository:
helm repo update percona -
Upgrade PMM:
helm upgrade pmm -f values.yaml percona/pmm -
After the upgrade, verify that PMM Server is running correctly:
kubectl get pods | grep pmm-server -
Check the logs for any errors:
kubectl logs deployment/pmm-server
Get expert help¶
If you need assistance, you can find comprehensive and free database knowledge on our community forum or blog posts. For professional support and services, contact our Percona Database Experts.