https://github.com/jfrog/charts
JFrog official Helm Charts
https://github.com/jfrog/charts
helm helm-charts kubernetes kubernetes-deployment
Last synced: 3 months ago
JSON representation
JFrog official Helm Charts
- Host: GitHub
- URL: https://github.com/jfrog/charts
- Owner: jfrog
- License: apache-2.0
- Created: 2018-08-13T10:31:39.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2025-09-27T09:42:02.000Z (3 months ago)
- Last Synced: 2025-10-05T22:36:04.293Z (3 months ago)
- Topics: helm, helm-charts, kubernetes, kubernetes-deployment
- Language: Shell
- Homepage: https://jfrog.com/integration/helm-repository/
- Size: 8.56 MB
- Stars: 273
- Watchers: 38
- Forks: 459
- Open Issues: 49
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# JFrog Helm Charts
This repository hosts the official **[JFrog](https://jfrog.com/) Helm Charts** for deploying **JFrog** products to [Kubernetes](https://kubernetes.io/)
For older version please refer to https://github.com/jfrog/charts/tree/pre-unified-platform
## Install Helm (only V3 is supported)
Get the latest [Helm release](https://github.com/helm/helm#install).
## Install Charts
### Add JFrog Helm repository
Before installing JFrog helm charts, you need to add the [JFrog helm repository](https://charts.jfrog.io) to your helm client.
```bash
helm repo add jfrog https://charts.jfrog.io
helm repo update
```
**Note:** For instructions on how to install a chart follow instructions in its _README.md_.
## Contributing to JFrog Charts
Fork the `repo`, make changes and then please run `make lint` to lint charts locally, and at least install the chart to see it is working. :)
On success make a [pull request](https://help.github.com/articles/using-pull-requests) (PR) on to the `master` branch.
We will take this PR changes internally, review and test.
Upon successful review , someone will give the PR a __LGTM__ (_looks good to me_) in the review thread.
We will add PR changes in upcoming releases and credit the contributor with PR link in changelog (and also closing the PR raised by contributor).
## Linting charts locally
**Note:** Docker must be running on your Mac/Linux machine.
The command will only lint changed charts.
To lint all charts:
```console
make lint
```
### Forcing to lint unchanged charts
**Note:** Chart version bump check will be ignored.
You can force to lint one chart with `--charts` flag:
```console
make lint -- --charts stable/artifactory
```
You can force to lint a list of charts (separated by comma) with `--charts` flag:
```console
make lint -- --charts stable/artifactory,stable/xray
```
You can force to lint all charts with `--all` flag:
```console
make lint -- --all
```
## Manually testing charts with Docker for Mac Kubernetes Cluster
**Note:** Make sure **'Show system containers (advanced)'** is enabled in `Preferences/Kubernetes`.
On the Mac you can install and test all changed charts in `Docker for Mac`:
```console
make mac
```
### Forcing to install unchanged charts
You can force to install one chart with `--charts` flag:
```console
make mac -- --charts stable/artifactory
```
You can force to install a list of charts (separated by comma) with `--charts` flag:
```console
make mac -- --charts stable/artifactory,stable/xray
```
You can force to install all charts with `--all` flag:
```console
make mac -- --all
```
**Note:** It might take a while to run install test for all charts in `Docker for Mac`.
## Manually testing charts with remote GKE cluster
You can install and test changed charts with `GKE` cluster set in kubeconfig `context`:
```console
make gke
```
### Forcing to install unchanged charts
You can force to install one chart with `--charts` flag:
```console
make gke -- --charts stable/artifactory
```
You can force to install a list of charts (separated by comma) with `--charts` flag:
```console
make gke -- --charts stable/artifactory,stable/xray
```
You can force to install all charts with `--all` flag:
```console
make gke -- --all
```
### Using dedicated GKE cluster for manual charts testing
By default it uses the `GKE` cluster set in kubeconfig `context`, you can specify the dedicated cluster (it must be set in the kubeconfig) in the file `CLUSTER`:
```
GKE_CLUSTER=gke_my_cluster_context_name
```
Then store the `CLUSTER` file in the root folder of the repo. It is also ignored by git.
In such setup your local default cluster can be different from the charts testing one.
## Examples
For more detailed examples of each chart values, please refer [examples](https://github.com/jfrog/charts/tree/master/examples).
## Docs
For more information on using Helm, refer to the Helm's [documentation](https://docs.helm.sh/using_helm/#quickstart-guide).
To get a quick introduction to Charts see this Chart's [documentation](https://docs.helm.sh/developing_charts/#charts).