We do not currently recommend upgrading to 2.6.x at this time. If you have questions, please reach out to us on Slack.
Upgrading to 2.6.5 from older versions involves a data migration. This migration can take a long time depending on the size of your cluster. If you are looking to upgrade a long-lived cluster, we recommend waiting for 2.7.0. For a newer cluster, if you still wish to upgrade, we recommend that you:
Backup your cluster before upgrading
Upgrade to 2.6.5 during a time when your cluster is not in use
Run the following check before upgrading:
pachctl misc test-migrations postgres://USERNAME:PASSWORD@HOST:PORT/pachyderm
Learn how to upgrade Pachyderm to access new features and performance enhancements.
Before You Start #
- Check the release notes before upgrading
- Back up your cluster
- Update your Helm chart values if applicable
How to Upgrade Pachyderm #
- Run the following brew command or download & install the latest release assets:
brew tap pachyderm/tap && brew install pachyderm/tap/pachctl@2.6 - Upgrade Helm.
Note that the repo name input (pachd) must match the name you provided upon first install.
You can also pass in a specific version (e.g., --version x.x.0-rc.1) if you are testing a pre-released version of Pachyderm.
helm repo update
helm upgrade pachyderm pachyderm/pachyderm -f my_pachyderm_values.yaml --set proxy.enabled=true --set proxy.service.type=LoadBalancer Note that the repo name input (pachd) must match the name you provided upon first install. You can also pass in a specific version (e.g., --version x.x.0-rc.1) if you are testing a pre-released version of Pachyderm.
helm repo update
helm upgrade pachyderm pachyderm/pachyderm --set deployTarget=LOCAL --set proxy.enabled=true --set proxy.service.type=LoadBalancer - Verify that the installation was successful by running
pachctl version:
pachctl version
# COMPONENT VERSION
# pachctl 2.6.10
# pachd 2.6.10