Platform Installation with Helm Charts

This page covers post-install configuration for the JFrog Platform Helm chart. If you have not yet installed, start with the Helm Quick Start.

For license requirements by product combination, see the License Matrix.

Install the License

Choose one of these methods to install the JFrog Platform license. Use only one method — switching methods while the cluster is running may disable the Artifactory HA cluster:

• Artifactory UI (recommended) — once the primary cluster is running, insert licenses via the UI.
• REST API — use the Install License API.
• Kubernetes Secret — create a Secret from a license file, or embed it inline in the Helm release. Applies to initial deployment only.

Enable Additional Products

The JFrog Platform Helm chart lets you enable or disable products after your initial install using a custom-values.yaml file and a helm upgrade command.

For example:

1. To deploy Xray, create a custom-values.yaml file with the following content.

   YAML

   xray:
     enabled: true

2. Run the upgrade command.

   Bash

   helm upgrade --install jfrog-platform --namespace jfrog-platform --create-namespace jfrog/jfrog-platform  -f custom-values.yaml

3. Configure each JFrog product separately with the following steps:

   1. Copy the configurations to update from the main values.yaml into a custom-values.yaml file.

   2. Set your custom values in custom-values.yaml.

      Any values not present in custom-values.yaml fall back to the defaults in the main values.yaml.

   3. Run the upgrade command.

      Bash

      helm upgrade --install jfrog-platform --namespace jfrog-platform --create-namespace jfrog/jfrog-platform  -f custom-values.yaml

📘

Note

If you install Xray with the JFrog Platform charts, the RabbitMQ vhost is named "xray". The standalone Xray Helm chart sets "/" as the RabbitMQ vhost.

JFrog Platform Product Configuration

Apply any of the following configurations after installation:

System YAML Configuration File

Configure all system settings using the system.yaml file in $JFROG_HOME/artifactory/var/etc. For more information, see System Configuration. If you do not have a system.yaml file in that folder, copy the template from the same directory and name it system.yaml.

📘

Note

Unlike other installations, you make changes in values.yaml; Helm applies them to system.yaml.

To apply configuration changes:

1. Update values.yaml.

2. Run the following command.

   Bash

   helm upgrade --install <jfrog product> --namespace <jfrog product> -f values.yaml

Database

The JFrog Platform Helm chart includes a bundled PostgreSQL database for evaluation use only. Configure an alternative supported database before deploying to production.

Customize Java Opts (Optional)

Set JVM parameters using the artifactory.extraJavaOpts property in $JFROG_HOME/artifactory/var/etc/system.yaml. Use the following Java memory parameters:

Scale -Xms and -Xmx with repository size and concurrent user count. With at least 512 MB reserved for Artifactory, the recommended minimal values are:

-server -Xms512m -Xmx2g -Xss256k -XX:+UseG1GC

For more recommendations about your hardware configuration, especially the -Xmx parameter, see System Requirements.

Additional Settings

Use additional settings to customize ports, join keys, and master keys. See joinKey (join.key) and masterKey (master.key).

Configure Filestore

By default, Artifactory uses the local file system for storage. It supports additional filestore configurations for cloud storage, custom binary providers, and redundancy.

Use an External PostgreSQL Database in the JFrog Platform Installation

Configure the JFrog Platform to use an external PostgreSQL database instead of the bundled one.

Create a values-external-postgresql.yaml file with the following YAML configuration.

global:
  database:
    initDBCreation: false
postgresql:
  enabled: false
artifactory:
  database:
    type: postgresql
    driver: org.postgresql.Driver
    url: 'jdbc:postgresql://${POSTGRESQL_HOST}:${POSTGRESQL_PORT}/${ARTIFACTORY_DATABASE}'
    user: ${ARTIFACTORY_DATABASE_USER}
    password: ${ARTIFACTORY_DATABASE_PASSWORD}
xray:
  database:
    url: 'postgres://${POSTGRESQL_HOST}:${POSTGRESQL_PORT}/${XRAY_DATABASE}?sslmode=disable'
    user: ${XRAY_DATABASE_USER}
    password: ${XRAY_DATABASE_PASSWORD}
distribution:
  database:
    url: 'jdbc:postgresql://${POSTGRESQL_HOST}:${POSTGRESQL_PORT}/${DISTRIBUTION_DATABASE}?sslmode=disable'
    user: ${DISTRIBUTION_DATABASE_USER}
    password: ${DISTRIBUTION_DATABASE_PASSWORD}

Set postgresql.enabled=false in the YAML file and provide the external database details. Create the database and users before running the Helm install or upgrade command.

For more information, see Using an External Database.

Access Logs

List pods to find the pod name:

kubectl --namespace <your namespace> get pods

Stream container logs:

kubectl --namespace <your namespace> logs -f <name of the pod> -c <name of the container>