JFrog Artifactory OSS is a free Artifactory edition to host Generic repositories.

Heads up: Our Helm Chart docs are moving to our main documentation site. For Artifactory installers, see Installing Artifactory.

• Kubernetes 1.19+

This chart will do the following:

• Deploy JFrog Artifactory OSS
• Deploy an optional Nginx server
• Deploy an optional PostgreSQL Database
• Optionally expose Artifactory with Ingress Ingress documentation

Before installing JFrog helm charts, you need to add the JFrog helm repository to your helm client.

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

To install the chart with the release name artifactory-oss:

helm upgrade --install artifactory-oss --set artifactory.postgresql.postgresqlPassword=<postgres_password> jfrog/artifactory-oss --namespace artifactory-oss --create-namespace

NOTE: If using artifactory or nginx service type LoadBalancer, it might take a few minutes for Artifactory OSS's public IP to become available.

Once you have a new chart version, you can upgrade your deployment with

helm upgrade artifactory-oss jfrog/artifactory-oss --namespace artifactory-oss --create-namespace

Arifactory 6.x to 7.x upgrade requires a one time migration process. This is done automatically on pod startup if needed. It's possible to configure the migration timeout with the following configuration in extreme cases. The provided default should be more than enough for completion of the migration.

artifactory:
  artifactory:
    # Migration support from 6.x to 7.x
    migration:
      enabled: true
      timeoutSeconds: 3600

• Note: If you are upgrading from 1.x to 3.x and above chart versions, please delete the existing statefulset of postgresql before upgrading the chart due to breaking changes in postgresql subchart.

kubectl delete statefulsets <OLD_RELEASE_NAME>-postgresql

• For more details about artifactory chart upgrades refer here

helm delete artifactory-oss --namespace artifactory-oss                                                                                                                                     

This will delete your Artifactory OSS deployment.
NOTE: You might have left behind persistent volumes. You should explicitly delete them with

kubectl delete pvc ...
kubectl delete pv ...

The Artifactory OSS chart comes with PostgreSQL deployed by default.
For details on the PostgreSQL configuration or customising the database, Look at the options described in the Artifactory helm chart.

To get Helm to create an ingress object with a hostname, add these two lines to your Helm command:

helm upgrade --install artifactory-oss \
  --set artifactory.nginx.enabled=false \
  --set artifactory.ingress.enabled=true \
  --set artifactory.ingress.hosts[0]="artifactory.company.com" \
  --set artifactory.artifactory.service.type=NodePort \
  jfrog/artifactory-oss --namespace artifactory-oss --create-namespace

To manually configure TLS, first create/retrieve a key & certificate pair for the address(es) you wish to protect. Then create a TLS secret in the namespace:

kubectl create secret tls artifactory-tls --cert=path/to/tls.cert --key=path/to/tls.key

Include the secret's name, along with the desired hostnames, in the Artifactory Ingress TLS section of your custom values.yaml file:

artifactory:
  artifactory:
    ingress:
      ## If true, Artifactory Ingress will be created
      ##
      enabled: true

      ## Artifactory Ingress hostnames
      ## Must be provided if Ingress is enabled
      ##
      hosts:
        - artifactory-oss.domain.com
      annotations:
        kubernetes.io/tls-acme: "true"
      ## Artifactory Ingress TLS configuration
      ## Secrets must be manually created in the namespace
      ##
      tls:
        - secretName: artifactory-tls
          hosts:
            - artifactory-oss.domain.com

https://www.jfrog.com https://www.jfrog.com/confluence/