Cloud customer?
 Upgrade in MyJFrog >

Search





Overview

The JFrog Platform upgrade enables you to upgrade a existing JFrog Artifactory standalone chart to a complete JFrog Platform, with all or some of the rest of the JFrog products.


Migrating Existing Artifactory Installations to the JFrog Platform

You can only migrate the following Artifactory installations:

  • Artifactory chart version 11.x and above (single mode)
  • Artifactory chart version 4.x and above (HA)

Before migrating an existing Artifactory installation to the JFrog Platform, you will need to verify that you are on the latest version of Artifactory (see Installing Artifactory - Helm Installation and Installing Artifactory - Helm HA Installation).

In addition, it is recommended to use an external PostgreSQL database for production grade deployments; the steps below assume you are using an external PostgreSQL database

There are two methods for migrating an existing Artifactory installation:

  • (Recommended) Option 1: Perform a system level import and export - this is the cleanest and easiest method
  • Option 2: Link the old Persistent Volume Claim (PVC)  - this option is intended for advanced users who have an existing big filestore already in place

Page Contents


(Recommended) Option 1: Perform a System Level Import and Export

Before migration, it is recommended to perform a System Level Import and Export.  Artifactory can export and import the entire Artifactory server, including configuration, security information, stored data, and metadata. The format used is identical to the System Backup format. This is useful when running manual backups and for migrating and restoring a complete Artifactory instance (as an alternative to using database level backup and restore).

  1. In the JFrog Platform, click the Administration tab, then navigate to Artifactory > Import & Export > System.

  2. In the Export System field, enter a location on the pod (/opt/jfrog/artifactory/var/backup), for the old release, then click Export.

  3. Install the Platform chart as a new release and copy the exported file to a location (/opt/jfrog/artifactory/var/backup).
  4. Export the file from the Platform chart UI.

Option 2: For Advanced Users - Linking the Old PersistentVolumeClaim (PVC)

If an existing installation has a lot of data, manually importing, and exporting may take a lot of time. Therefore, you will want to link to the old PVC to save this time (advanced users only).

Artifactory Single Node

  1. Link the old PVC of the Artifactory chart to the new JFrog Platform chart release.
  2. Enable the Artifactory subchart in the JFrog Platform release, and then perform a Helm upgrade. The old PVC should be provided as an existing claim.
  3. Create a custom-values.yaml file with the following configuration.

    global:
      initDBCreation: false        
    postgresql:
      enabled: false
    rabbitmq:
      enabled: false
    redis:
      enabled: false
    artifactory:
      enabled: true
      artifactory:
        persistence:
          enabled: true
          existingClaim: artifactory-volume-<OLD RELEASE NAME>-artifactory-0
    artifactory-ha:
      enabled: false
    xray:
      enabled: false
    distribution:
      enabled: false
    mission-control:
      enabled: false
    pipelines:
      enabled: false
    
    helm upgrade --install jfrog-platform stable/jfrog-platform -f custom-values.yaml
  4. Verify that the upgrade and old Helm release can be uninstalled. Make sure that the old PVC is not removed.

Artifactory HA

Important

When installing the JFrog Platform chart, make sure to use the <old-release-name>. This will reuse the existing PVCs of the old release.

  1. Reuse the old PVC of the Artifactory chart in the new JFrog Platform chart release. 
    The Artifactory HA chart does not have the option of providing an existing claim name for the PVC; instead you will need to create a PVC using a defined name. For more information, see Using an Existing Volume Claim in Helm Charts for Advanced Users.

  2. Uninstall the existing release using helm uninstall <old-release-name> . This will uninstall everything except the PVCs; PVCs can exist with names such as volume-<old-release-name>-artifactory-ha-primary-0 and volume-<old-release-name>-artifactory-ha-member-<ordinal-number>depending upon the number of node replica sets defined.
  3. Enable the Artifactory subchart in the JFrog Platform release and perform a Helm upgrade.
  4. Create a custom-values.yaml file with the following configuration.

    global:
      initDBCreation: false        
    postgresql:
      enabled: true
    rabbitmq:
      enabled: false
    redis:
      enabled: false
    artifactory:
      enabled: false
    artifactory-ha:
      enabled: true
    xray:
      enabled: false
    distribution:
      enabled: false
    mission-control:
      enabled: false
    pipelines:
      enabled: false
    
    helm upgrade --install <old-release-name> stable/jfrog-platform -f custom-values.yaml





Copyright © 2021 JFrog Ltd.