As we reach the end of September 2024, ThreadFix version 3.x on-premises has officially reached its End-of-Life. Therefore, there is no longer support or updates for this version of the product. We have fully transitioned our product and development teams to focus ThreadFix SaaS and migrating all customers over from the on-premises versions. Our Customer Success and Support teams are here to help you in migrating to ThreadFix SaaS and maximizing the value you see from this improved offering from Coalfire. This is the next phase of ThreadFix and our team is looking forward to continuing to support you on this journey.
Adjusting Helm Values
You will learn
How to change Helm values in ThreadFix. The following is suitable for all supported distributions of Kubernetes.
Prerequisites
Audience: IT Professional
Difficulty: Basic
Time needed: Approximately 10 minutes
Tools required: See Pre-requisites list below
Pre-requisites list:
ThreadFix instance running in Kubernetes
kubectl access to Kubernetes cluster
Helm version greater than 3.5
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')
Validate that the TF_RELEASE and TF_VERSION parameters are set.
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:
Export the currently installed Helm values.
Make necessary changes to the myValues.yaml file.
Upgrade ThreadFix with Helm
Validate the update 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.
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.