JFrog Container Registry Helm Chart
JFrog Container Registry is a free Artifactory edition with Docker and Helm repositories support.
Heads up: Our Helm Chart docs are moving to our main documentation site. For Artifactory installers, see Installing Artifactory.
- Kubernetes 1.12+
This chart will do the following:
- Deploy JFrog Container Registry
- Deploy an optional Nginx server
- Deploy an optional PostgreSQL Database
- Optionally expose Artifactory with Ingress Ingress documentation
Installing the Chart
Add ChartCenter Helm repository
Before installing JFrog helm charts, you need to add the ChartCenter helm repository to your helm client.
helm repo add center https://repo.chartcenter.io helm repo update
To install the chart with the release name
helm upgrade --install jfrog-container-registry --set artifactory.postgresql.postgresqlPassword=<postgres_password> --namespace artifactory-jcr center/jfrog/artifactory-jcr
Accessing JFrog Container Registry
NOTE: If using artifactory or nginx service type
LoadBalancer, it might take a few minutes for JFrog Container Registry’s public IP to become available.
Updating JFrog Container Registry
Once you have a new chart version, you can upgrade your deployment with
helm upgrade jfrog-container-registry center/jfrog/artifactory-jcr
Special Upgrade Notes
Artifactory upgrade from 6.x to 7.x (App Version)
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.
bash kubectl delete statefulsets <OLD_RELEASE_NAME>-postgresql* For more details about artifactory chart upgrades refer here ### Deleting JFrog Container Registry On helm v2:
bash helm delete --purge jfrog-container-registry
On helm v3:
helm delete jfrog-container-registry --namespace artifactory-jcr ``` This will delete your JFrog Container Registry deployment.<br> **NOTE:** You might have left behind persistent volumes. You should explicitly delete them with ```bash kubectl delete pvc ... kubectl delete pv ...
The JFrog Container Registry 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.
Ingress and TLS
To get Helm to create an ingress object with a hostname, add these two lines to your Helm command:
helm upgrade --install jfrog-container-registry \ --set artifactory.nginx.enabled=false \ --set artifactory.ingress.enabled=true \ --set artifactory.ingress.hosts="artifactory.company.com" \ --set artifactory.artifactory.service.type=NodePort \ --namespace artifactory-jcr center/jfrog/artifactory-jcr
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
artifactory: artifactory: ingress: ## If true, Artifactory Ingress will be created ## enabled: true ## Artifactory Ingress hostnames ## Must be provided if Ingress is enabled ## hosts: - jfrog-container-registry.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: - jfrog-container-registry.domain.com