JanusGraph is a scalable graph database capable of handling an extremely large number of vertices and edges. It has a pluggable architecture that allows for choice of storage and indexing backends.

This chart bootstraps a JanusGraph deployment on a Kubernetes cluster using the Helm package manager.

• Kubernetes 1.7

To install the chart with the release name my-release:

helm install --name my-release stable/janusgraph

To delete the chart with the release name my-release:

helm delete janusgraph --purge

Use the default values.yaml to gain an understanding of the ways in which you can customize this chart.

Some common properties and their usage have been referenced in the values.yaml file.

Specify your own parameters using the --set key=value[,key=value] argument to helm install.

Alternatively, your own YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

helm install --name my-release -f values.yaml stable/janusgraph

JanusGraph specific properties are nested under the properties key.

A full list of JanusGraph properties are defined provided in the JanusGraph configuration reference.

When deployed with local storage, the JanusGraph image stores the graph and index data at the /db path of the container.

By default, the chart mounts a Persistent Volume at this location. The volume is created using dynamic volume provisioning and will be cleaned up when the chart is deleted. To persist data outside of this lifecycle of this chart, choose a remote storage backend or bring your own Persistent Volume Claim:

$ helm install --set persistence.existingClaim=<your-persistent-volume-claim> stable/janusgraph