How to install ThreadFix 3.1 with a private Docker registry.
Prerequisites
Audience: IT Professional Difficulty: Intermediate Time needed: Approximately 10 minutes Tools required: If any
Internally developed containers follow the bitnami imageRegistry pattern so all ThreadFix and bitnami images can be set to use a different registry by setting the parameter global.imageRegistry in Helm values.
Other 3rd-party containers used by ThreadFix do not follow this convention and must be manually set per container. The list of images may change from release to release.
Retrieve images needed by ThreadFix
If the ThreadFix helm repository has not been installed, add it with the following command:
Follow the user’s company’s policies and procedures to add these images to the private docker registry
Installing with private Docker registry
If the user’s private repository is a mirror of public repositories or follows the same naming conventions as public repositories, use the following instructions.
Create myValues dir (if it does not already exist).
mkdir -p myValues
Set the name of the private registry (replace <imageRegistry> with the appropraite value).
IMAGE_REGISTRY=<imageRegistry>
Create a registry.yaml file with the following contents (replace <imageRegistry>) with the fqdn of the user’s private registry):
Installing with private Docker registry and custom repository names
If the user’s private image registry uses different names for repositories, change each repository name to the name of the image being used.
Create myValues dir (if it does not already exist)
mkdir -p myValues
Create a repositories.yaml file in the myValues directory with the following content (replace <imageRegistry> with the FQDN of the user’s registry and <imageRepository> with the name of the container's corresponding image).