Pipelines HA Installation

Extract the installer from the downloaded .rpm, .deb, or .tar.gz file, as shown for the single node installation.

Perform the install procedure in the first node using the Pipelines command line installer.

$ sudo pipelines install \
    --base-url <jfrog-url> \
    --artifactory-joinkey <join-key> \
    --db-connection-string postgres://<user>:<pass>@<ip>:<port>/<db> \
    --installer-ip <new-instance-ip> \
    --api-url http://<new-instance-ip>:8082/pipelines/api \

Note: You will need to fetch your jfrogURL (custom base URL) and join key to link your Pipelines installation to the Platform.

You may perform a health check on the node to confirm it is operating properly.

In the new node instance, extract the installer from the downloaded .rpm, .deb, or .tar.gz file, as performed for the first node.

Copy from the first node instance the file $JFROG_HOME /pipelines/var/etc/system.yaml to the same location in the new instance.

Perform the install procedure in the new node using the Pipelines command line installer.

You may perform a health check on the node to confirm it is operating properly.

Add the JFrog Helm repository to your Helm client.

helm repo add jfrog https://charts.jfrog.io

Update the repository.

helm repo update

Next, create a unique master key; Pipelines requires a unique master key to be used by all micro-services in the same cluster. By default the chart has one set, the pipelines.masterKey, in the values.yaml file (unlike other installations, Helm Chart configurations are made to the values.yaml and are then applied to the system.yaml).

Generate a unique key and pass it to the template during installation/upgrade.

# Create a key
export MASTER_KEY=$(openssl rand -hex 32)
echo ${MASTER_KEY}
 
# Pass the created master key to Helm
helm upgrade --install --set pipelines.masterKey=${MASTER_KEY} --namespace pipelines jfrog/pipelines

Alternatively, you can create a secret containing the master key manually and pass it to the template during installation/upgrade.

# Create a key
export MASTER_KEY=$(openssl rand -hex 32)
echo ${MASTER_KEY}
 
# Create a secret containing the key. The key in the secret must be named master-key
kubectl create secret generic my-secret --from-literal=master-key=${MASTER_KEY}
 
# Pass the created secret to Helm
helm upgrade --install pipelines --set pipelines.masterKeySecretName=my-secret --namespace pipelines jfrog/pipelines

To connect Pipelines to your Artifactory installation, you will need to use a Join Key. To provide a Join Key, jfrogUrl, and jfrogUrlUI to your Pipelines installation, retrieve the connection details of your Artifactory installation from the UI in the following way (for more information see Viewing the Join Key.Introduction to the General Security Settings

pipelines:
  ## Artifactory URL - Mandatory
  ## If Artifactory and Pipelines are in same namespace, jfrogUrl is Artifactory service name, otherwise its external URL of Artifactory
  jfrogUrl: ""  
   
  ## Artifactory UI URL - Optional
  ## This must be the external URL of Artifactory, for example: https://artifactory.example.com
  ## If you provide a value here, it overrides the JFrog Platform Custom URL. A custom URL is necessary for Pipelines to function.
  ##If JFrog Platform Custom URL does not exist,You must provide a value with the installation or configure the custom URL through UI after installation.
  jfrogUrlUI: ""    ## Join Key to connect to Artifactory    ## Join Key to connect to Artifactory
  
  ## IMPORTANT: You should NOT use the example joinKey for a production deployment!
  joinKey: EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE
 
  ## Pipelines requires a unique master key
  ## You can generate one with the command: "openssl rand -hex 32"
  ## IMPORTANT: You should NOT use the example masterKey for a production deployment!
  masterKey: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

You can choose to set the Redis password in the values.yaml file and pass it with the installation by setting redis.usePassword set as true.

The following snippet shows the configuration.

redis:
  password: "password"
  usePassword: true

Get the Pipelines helm chart to get the required configuration files.

helm fetch jfrog/pipelines --untar

Configure the installation by editing the local copies of the values-ingress.yaml and values-ingress-passwords.yaml with the required configuration values.

1. Edit the URLs in the values-ingress.yamlfile (Artifactory URL, Ingress hosts, Ingress tls secrets).

2. Set the passwords uiUserPassword, postgresqlPassword and auth.password in the local copies.

3. Set the masterKey and joinKey in the values-ingress-passwords.yaml.

   Note

   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 pipelines --namespace pipelines -f values.yaml

Install Pipelines.

kubectl create ns pipelines
helm upgrade --install pipelines --namespace pipelines jfrog/pipelines -f pipelines/values-ingress.yaml -f pipelines/values-ingress-passwords.yaml

Access Pipelines from your browser at: http://<jfrogUrl>/ui/, then go to the Pipelines tab in the Application module in the UI.

Check the status of your deployed helm releases.

helm status pipelines