Insight HA Helm Installation

JFrog Installation & Setup Documentation

Content Type
Installation & Setup


Currently, it is not possible to connect a JFrog product (like Insight) that is within a Kubernetes cluster with another JFrog product (like Artifactory) that is outside of the cluster, as this is considered a separate network. Therefore, JFrog products cannot be joined together if one of them is in a cluster.

Deploying Artifactory for Small, Medium or Large Installations

In the chart directory, includes three values files, one for each installation type–small/medium/large. These values files are recommendations for setting resources requests and limits for your installation. You can find the files in the corresponding chart directory:

High Availability

For high availability of Insight, set the replicaCount in the values.yaml file to >1 (the recommended value is 3).

helm upgrade --install insight --namespace insight --set replicaCount=3 jfrog/insight
  1. Add the to your Helm client.

    helm repo add jfrog
  2. Update the repository.

    helm repo update
  3. Initiate installation by providing a join key and JFrog url as a parameter to the Insight chart installation.

    helm upgrade --install insight --set insight.joinKey=<YOUR_PREVIOUSLY_RETIREVED_JOIN_KEY> \
                 --set insightServer.jfrogUrl=<YOUR_PREVIOUSLY_RETIREVED_BASE_URL> --namespace insight jfrog/insight

    Alternatively, you can manually create a secret containing the join key and then pass it to the template during install/upgrade. the key must be named join-key.

    # Create a secret containing the key:
    kubectl create secret generic my-secret --from-literal=join-key=<YOUR_PREVIOUSLY_RETIREVED_JOIN_KEY>
    # Pass the created secret to helm
    helm upgrade --install insight --set insight.joinKeySecretName=my-secret --namespace insight jfrog/insight


    In either case, make sure to pass the same join key on all future calls to helm install and helm upgrade! This means always passing --set insight.joinKey=<YOUR_PREVIOUSLY_RETIREVED_JOIN_KEY>. In the second, this means always passing --set missionControl.joinKeySecretName=my-secret and ensuring the contents of the secret remain unchanged.

  4. Customize the product configuration (optional) including database, Java Opts, and filestore.


    Unlike other installations, Helm Chart configurations are made to the values.yaml and are then applied to the system.yaml.

    Follow these steps to apply the configuration changes.

    1. Make the changes to values.yaml.

    2. Run the command.

      helm upgrade -- install insight --namespace insight -f values.yaml

    3. Restart Insight to apply the changes.

  5. Access Insight from your browser at: http://<jfrogUrl>/ui/ and go to the Dashboard tab in the Application module in the UI.

  6. Check the status of your deployed Helm releases.

    helm status insight