Upgrade
You will learn
How to upgrade a Kubernetes deployment of ThreadFix with Helm.
Prerequisites
Audience: IT Professional
Difficulty: Basic
Time needed: Approximately 10 minutes
Tools required: See Pre-requisites list below
Prior to beginning any upgrades or migration, ThreadFix strongly recommends users review the Upgrade & Migration Guidelines.
Pre-requisites list
ThreadFix instance running in Kubernetes
kubectl access to Kubernetes cluster
Helm version greater than 3.5
Users upgrading from 3.1.2 please view the 3.2 Release Notes for a potential additional upgrade step.
Upgrading
Enter the following commands on a command line to perform the described action.
Add the Denim Group Helm repository if not present:
helm repo add denimgroup https://threadfix-downloads.s3-us-west-2.amazonaws.com/helm/
Â
Backup the ThreadFix instance by following the Backup & Restore guide.
Get the Helm release name for the ThreadFix instance.
TF_RELEASE=$(helm ls | grep threadfix | awk '{print $1}')
Â
Get the current installed version of ThreadFix.
TF_VERSION=$(helm ls --filter "$TF_RELEASE" | grep -o 'threadfix-[Az0-9\.\-]*' | sed 's|threadfix-||g')
Â
ThreadFix automatically generates internal credentials if not explicitly provided. If not already done so, save these in a secure location for recovery purposes.
Network properties:
Database password:
Postgres password:
ESAPI encryption keys:
Â
Pull the latest chart from Denim Group's Helm repository for ThreadFix.
Â
Check the latest available version.
Â
Review the release notes prior to upgrading. Not all upgrade paths are supported.
(Optional) If changes to the charts values are required:
Export the currently installed Helm values.
Make necessary changes to the myValues.yaml file.
Pass the modified values file in the the helm upgrade command with -f myValues.yaml.
Upgrade ThreadFix with Helm (include -f myValues.yaml if modifying installation values).
Â
Follow the Upgrade Validation Checklist to validate the ThreadFix upgrade has completed successfully. If there are any issues, users may rollback to the previous state with:
If rolling back a failed upgrade, the user may have to restore the database from backup depending on the status of the database migration. Follow Backup & Restore for more information.
Table of Contents
- 1 You will learn
- 1.1 Prerequisites
- 1.1.1 Pre-requisites list
- 1.2 Upgrading
- 1.1 Prerequisites
- 2 Table of Contents
www.threadfix.it | www.coalfire.com
Copyright © 2024 Coalfire. All rights reserved.
This Information Security Policy is CoalFire - Public: Distribution of this material is not limited.