This repository contains Helm charts for deploying JupiterOne integrations in your Kubernetes cluster using the JupiterOne Integration Operator.
- Kubernetes cluster (1.19+)
- Helm 3.0+
- JupiterOne account with API access
- JupiterOne Integration Operator installed in your cluster
Add the JupiterOne Helm repository:
helm repo add jupiterone https://jupiterone.github.io/helm-charts
helm repo updateSearch for available charts:
helm search repo jupiterone| Chart | Description |
|---|---|
jupiterone-integration-operator |
The operator that manages integration instances |
jupiterone-integration-runner |
The runner that executes integration jobs |
Integration charts create IntegrationInstance custom resources that are managed by the operator. Available integrations include:
github- GitHub integrationgitlab- GitLab integrationjira- Jira integrationbitbucket- Bitbucket integrationjenkins- Jenkins integrationartifactory- JFrog Artifactory integrationhashicorp-vault- HashiCorp Vault integrationterraform-cloud- Terraform Cloud integration- And many more...
Run helm search repo jupiterone for the complete list.
- First, ensure the operator and runner are installed:
helm install j1-operator jupiterone/jupiterone-integration-operator \
--namespace jupiterone \
--create-namespace
helm install j1-runner jupiterone/jupiterone-integration-runner \
--namespace jupiterone- Install an integration chart with your configuration:
helm install my-github jupiterone/github \
--namespace jupiterone \
--set secret.selectedAuthType="token" \
--set secret.githubAppToken="your-token"Or create a values file:
# values.yaml
collectorName: runner
pollingInterval: "ONE_DAY"
secret:
selectedAuthType: "token"
githubAppToken: "your-github-token"helm install my-github jupiterone/github \
--namespace jupiterone \
-f values.yamlEach integration chart supports the following common configuration options:
| Parameter | Description | Default |
|---|---|---|
collectorName |
Name of the IntegrationRunner in the same namespace | runner |
pollingInterval |
How often the integration runs | ONE_WEEK |
secretName |
Name of the Kubernetes secret for credentials | <integration>-secret |
createSecret |
Whether to create the secret from values | true |
Polling interval options:
DISABLEDTHIRTY_MINUTESONE_HOURFOUR_HOURSEIGHT_HOURSTWELVE_HOURSONE_DAYONE_WEEK
For integration-specific configuration options, see the values.yaml file in each chart or run:
helm show values jupiterone/<chart-name>If you prefer to manage secrets outside of Helm (e.g., using External Secrets Operator or sealed-secrets):
- Create your secret manually with the required keys
- Install the chart with
createSecret: falseand provide the secret name:
helm install my-github jupiterone/github \
--namespace jupiterone \
--set createSecret=false \
--set secretName=my-existing-secrethelm repo update
helm upgrade my-github jupiterone/github --namespace jupiteronehelm uninstall my-github --namespace jupiteroneFor information about generating and maintaining these charts, see the chartgen documentation.
For issues with these Helm charts, please open an issue in this repository.
For JupiterOne platform support, visit jupiterone.io.