[{"_1":2,"_139":-5,"_140":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_133":134},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_27":28,"_29":30,"_59":60,"_61":-7,"_62":-7,"_63":-7,"_64":-7,"_65":-5,"_66":-5,"_67":11,"_68":11,"_52":69,"_123":21,"_91":92,"_124":90,"_125":51,"_35":36,"_126":11,"_127":21,"_128":129,"_130":-5,"_131":11,"_132":11},"scanningType","none","tagData",{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},"content_type","image","creator",29930447,"digest","sha256:c3327ffd7e32330666316d97aa97a2066f0a98e885e6a01e6b58cd0f2a7db42b","full_size",7947,"id",888242369,"images",[],"last_updated","2025-04-25T11:56:21.153682Z","last_updater","last_updater_username","bitnamirobot","media_type","application/vnd.oci.image.index.v1+json","name","sha256-039f4c990b367ed2c6774719a602cc26501c42144c59576636e6a497f9d29392","repository",23979171,"tag_last_pulled","tag_last_pushed","tag_status","inactive","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom","scoutSummary","staticSummary","isScoutPaymentRequired","canSeeVulnerabilities",{"_70":71,"_76":77,"_79":80,"_81":82,"_83":11,"_43":84,"_85":86,"_87":88,"_50":90,"_91":92,"_93":94,"_95":-5,"_96":97,"_98":99,"_100":101,"_102":-5,"_103":97,"_104":105,"_106":11,"_107":92,"_108":109,"_114":11,"_115":116,"_120":92,"_121":122},"categories",[72],{"_50":73,"_74":75},"Databases & storage","slug","databases-and-storage","content_types",[78,32],"helm","date_registered","2024-04-30T15:05:52.535132Z","description","Bitnami Helm chart for JanusGraph","is_private","2025-08-26T02:59:47.336571Z","last_modified","2026-03-16T14:24:00.837876Z","media_types",[89,49],"application/vnd.cncf.helm.config.v1+json","janusgraph","namespace","bitnamicharts","pull_count",435910,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","\n\n# Bitnami Secure Images Helm chart for JanusGraph\n\nJanusGraph is a scalable graph database optimized for storing and querying graphs containing hundreds of billions of vertices and edges distributed across a multi-machine cluster.\n\n[Overview of JanusGraph](https://janusgraph.org/)\n\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/janusgraph\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository.\n\n## Introduction\n\nThis chart bootstraps a [JanusGraph](https://github.com/bitnami/containers/tree/main/bitnami/janusgraph) deployment on a [Kubernetes](https://kubernetes.io) cluster using the [Helm](https://helm.sh) package manager.\n\n## Before you begin\n\n- Kubernetes 1.23+\n- Helm 3.8.0+\n\n## Installing the Chart\n\nTo install the chart with the release name `my-release`:\n\n```console\nhelm install my-release oci://REGISTRY_NAME/REPOSITORY_NAME/janusgraph\n```\n\n> Note: You need to substitute the placeholders `REGISTRY_NAME` and `REPOSITORY_NAME` with a reference to your Helm chart registry and repository. For example, in the case of Bitnami, you need to use `REGISTRY_NAME=registry-1.docker.io` and `REPOSITORY_NAME=bitnamicharts`.\n\nThe command deploys JanusGraph on the Kubernetes cluster in the default configuration. The [Parameters](#parameters) section lists the parameters that can be configured during installation.\n\n> **Tip**: List all releases using `helm list`\n\n## Uninstalling the Chart\n\nTo uninstall/delete the `my-release` deployment:\n\n```console\nhelm delete my-release\n```\n\nThe command removes all the Kubernetes components associated with the chart and deletes the release.\n\n## Configuration and installation details\n\nThis section describes credentials, configuration, and other installation options.\n\n### [Rolling VS Immutable tags](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-understand-rolling-tags-containers-index.html)\n\nIt is strongly recommended to use immutable tags in a production environment. This ensures your deployment does not change automatically if the same tag is updated with a different image.\n\nBitnami will release a new chart updating its containers if a new version of the main container, significant changes, or critical vulnerabilities exist.\n\n### Prometheus metrics\n\nThis chart can be integrated with Prometheus by setting `metrics.enabled` to `true`. This will deploy a sidecar container with [jmx_exporter](https://github.com/prometheus/jmx_exporter) in all pods and a `metrics` service, which can be configured under the `metrics.service` section. This `metrics` service will have the necessary annotations to be automatically scraped by Prometheus.\n\n#### Prometheus requirements\n\nIt is necessary to have a working installation of Prometheus or Prometheus Operator for the integration to work. Install the [Bitnami Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/prometheus) or the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) to easily have a working Prometheus in your cluster.\n\n#### Integration with Prometheus Operator\n\nThe chart can deploy `ServiceMonitor` objects for integration with Prometheus Operator installations. To do so, set the value `metrics.serviceMonitor.enabled=true`. Ensure that the Prometheus Operator `CustomResourceDefinitions` are installed in the cluster or it will fail with the following error:\n\n```text\nno matches for kind \"ServiceMonitor\" in version \"monitoring.coreos.com/v1\"\n```\n\nInstall the [Bitnami Kube Prometheus helm chart](https://github.com/bitnami/charts/tree/main/bitnami/kube-prometheus) for having the necessary CRDs and the Prometheus Operator.\n\n### External storage backend support\n\nYou may want to have JanusGraph connect to an external storage backend rather than installing one inside your cluster. Typical reasons for this are to use a managed database service, or to share a common database server for all your applications. To achieve this, the chart allows you to specify credentials for an external database with the [`storageBackend.external` parameter](#parameters). You should also disable the Cassandra installation with the `storageBackend.cassandra.enabled` option. Here is an example:\n\n```console\nstorageBackend.cassandra.enabled=false\nstorageBackend.external.backend=\nstorageBackend.external.hostname=\nstorageBackend.external.port=\n#Auth only if needed#\nstorageBackend.external.username=\nstorageBackend.external.existingSecret=\nstorageBackend.external.existingSecretPasswordKey=\n```\n\n### External indexing backend support\n\nYou may want to have JanusGraph connect to an external indexing backend. To achieve this, the chart allows you to specify credentials for an external indexing backend with the [`indexBackend.external` parameter](#parameters). Here is an example:\n\n```console\nindexBackend.external.backend=\nindexBackend.external.hostname=\nindexBackend.external.port=\n```\n\n### Backup and restore\n\nTo back up and restore Helm chart deployments on Kubernetes, you need to back up the persistent volumes from the source deployment and attach them to a new deployment using [Velero](https://velero.io/), a Kubernetes backup/restore tool. Find the instructions for using Velero in [this guide](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/apps-tutorials-backup-restore-deployments-velero-index.html).\n\n### Additional environment variables\n\nIn case you want to add extra environment variables (useful for advanced operations like custom init scripts), you can use the `extraEnvVars` property.\n\n```yaml\nextraEnvVars:\n - name: LOG_LEVEL\n value: error\n```\n\nAlternatively, you can use a ConfigMap or a Secret with the environment variables. To do so, use the `extraEnvVarsCM` or the `extraEnvVarsSecret` values.\n\n### Sidecars\n\nIf additional containers are needed in the same pod as JanusGraph (such as additional metrics or logging exporters), they can be defined using the `sidecars` parameter.\n\n```yaml\nsidecars:\n- name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nIf these sidecars export extra ports, extra port definitions can be added using the `service.extraPorts` parameter (where available), as shown in the example below:\n\n```yaml\nservice:\n extraPorts:\n - name: extraPort\n port: 11311\n targetPort: 11311\n```\n\n> NOTE: This Helm chart already includes sidecar containers for the Prometheus exporters (where applicable). These can be activated by adding the `--enable-metrics=true` parameter at deployment time. The `sidecars` parameter should therefore only be used for any extra sidecar containers.\n\nIf additional init containers are needed in the same pod, they can be defined using the `initContainers` parameter. Here is an example:\n\n```yaml\ninitContainers:\n - name: your-image-name\n image: your-image\n imagePullPolicy: Always\n ports:\n - name: portname\n containerPort: 1234\n```\n\nLearn more about [sidecar containers](https://kubernetes.io/docs/concepts/workloads/pods/) and [init containers](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/).\n\n### Pod affinity\n\nThis chart allows you to set your custom affinity using the `affinity` parameter. Find more information about Pod affinity in the [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity).\n\nAs an alternative, use one of the preset configurations for pod affinity, pod anti-affinity, and node affinity available at the [bitnami/common](https://github.com/bitnami/charts/tree/main/bitnami/common#affinities) chart. To do so, set the `podAffinityPreset`, `podAntiAffinityPreset`, or `nodeAffinityPreset` parameters.\n\n### FIPS parameters\n\nThe FIPS parameters only have effect if you are using images from the [Bitnami Secure Images catalog](https://go-vmware.broadcom.com/contact-us).\n\nFor more information on this new support, please refer to the [FIPS Compliance section](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/security-frameworks-FIPS-compliance.html).\n\n## Parameters\n\nThe following subsections list global, common, and component-specific parameters.\n\n### Global parameters\n\n| Name | Description | Value |\n| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ |\n| `global.imageRegistry` | Global Docker image registry | `\"\"` |\n| `global.imagePullSecrets` | Global Docker registry secret names as an array | `[]` |\n| `global.defaultStorageClass` | Global default StorageClass for Persistent Volume(s) | `\"\"` |\n| `global.storageClass` | DEPRECATED: use global.defaultStorageClass instead | `\"\"` |\n| `global.defaultFips` | Default value for the FIPS configuration (allowed values: '', restricted, relaxed, off). Can be overridden by the 'fips' object | `restricted` |\n| `global.security.allowInsecureImages` | Allows skipping image verification | `false` |\n| `global.compatibility.openshift.adaptSecurityContext` | Adapt the securityContext sections of the deployment to make them compatible with Openshift restricted-v2 SCC: remove runAsUser, runAsGroup and fsGroup and let the platform use their allowed default IDs. Possible values: auto (apply if the detected running cluster is Openshift), force (perform the adaptation always), disabled (do not perform adaptation) | `auto` |\n\n### Common parameters\n\n| Name | Description | Value |\n| --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |\n| `kubeVersion` | Override Kubernetes version | `\"\"` |\n| `apiVersions` | Override Kubernetes API versions reported by .Capabilities | `[]` |\n| `nameOverride` | String to partially override common.names.name | `\"\"` |\n| `fullnameOverride` | String to fully override common.names.fullname | `\"\"` |\n| `namespaceOverride` | String to fully override common.names.namespace | `\"\"` |\n| `commonLabels` | Labels to add to all deployed objects | `{}` |\n| `commonAnnotations` | Annotations to add to all deployed objects | `{}` |\n| `clusterDomain` | Kubernetes cluster domain name | `cluster.local` |\n| `extraDeploy` | Array of extra objects to deploy with the release | `[]` |\n| `diagnosticMode.enabled` | Enable diagnostic mode (all probes will be disabled and the command will be overridden) | `false` |\n| `diagnosticMode.command` | Command to override all containers in the deployment | `[\"sleep\"]` |\n| `diagnosticMode.args` | Args to override all containers in the deployment | `[\"infinity\"]` |\n| `storageBackend.usePasswordFiles` | Mount credentials as a files instead of using an environment variable | `true` |\n| `storageBackend.cassandra.enabled` | Use Apache Casandra subchart as storage backend | `true` |\n| `storageBackend.berkeleyje.enabled` | Use BerkeleyDB (local) as storage backend | `false` |\n| `storageBackend.berkeleyje.directory` | Path for the BerkeleyDB data | `/bitnami/janusgraph/data/storage` |\n| `storageBackend.external.backend` | Type of the external storage backend to be used | `\"\"` |\n| `storageBackend.external.hostname` | Hostname of the external storage backend | `\"\"` |\n| `storageBackend.external.port` | Port of the external storage backend | `\"\"` |\n| `storageBackend.external.username` | Username used to authenticate to the storage backend, in case it requires authentication | `\"\"` |\n| `storageBackend.external.existingSecret` | Existing secret containing the password of the external storage backend, in case its needed | `\"\"` |\n| `storageBackend.external.existingSecretPasswordKey` | Name of an existing secret key containing the storage backend password | `\"\"` |\n| `indexBackend.lucene.enabled` | Use Lucene (local) as index management backend | `false` |\n| `indexBackend.lucene.directory` | Path for the BerkeleyDB data | `/bitnami/janusgraph/data/index` |\n| `indexBackend.external.backend` | Type of the external index backend to be used | `\"\"` |\n| `indexBackend.external.hostname` | Hostname of the external index backend | `\"\"` |\n| `indexBackend.external.port` | Port of the external index backend | `\"\"` |\n| `cache.enabled` | Enable Janusgraph cache feature | `true` |\n| `existingConfigmap` | The name of an existing ConfigMap with your custom configuration for JanusGraph | `\"\"` |\n| `extraJanusgraphProperties` | Additional JanusGraph to be appended at the end of the janusgraph.properties configmap | `\"\"` |\n| `janusgraphProperties` | Override the content of the janusgraph.properties file. | `\"\"` |\n| `javaOptions` | Java options for JanusGraph execution | `\"\"` |\n| `image.registry` | JanusGraph image registry | `REGISTRY_NAME` |\n| `image.repository` | JanusGraph image repository | `REPOSITORY_NAME/janusgraph` |\n| `image.digest` | JanusGraph image digest in the way sha256:aa.... Please note this parameter, if set, will override the tag image tag (immutable \n\n_Note: the README for this chart is longer than the DockerHub length limit of 25000, so it has been trimmed. The full README can be found at https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-app-doc/apps-charts-janusgraph-index.html_","has_starred","hub_user","immutable_tags_settings",{"_110":11,"_111":112},"enabled","rules",[113],".*","is_automated","permissions",{"_117":21,"_118":11,"_119":11},"read","write","admin","user","storage_size",5426611,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","showSbxLogoOverride","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_27":28,"_63":-7,"_61":-7,"_62":-7,"_29":135,"_35":36,"_137":-7,"_138":11},{"_31":32,"_33":34,"_35":36,"_37":38,"_39":40,"_41":136,"_43":44,"_45":34,"_46":47,"_48":49,"_50":51,"_52":53,"_54":-5,"_55":44,"_56":57,"_58":21},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

bitnamicharts/janusgraph:sha256-039f4c990b367ed2c6774719a602cc26501c42144c59576636e6a497f9d29392