Skip to content
This repository was archived by the owner on Jan 19, 2024. It is now read-only.

Commit a4aece5

Browse files
author
Andrew Jefferson
committed
adding SSL information to the docs
1 parent c4538b6 commit a4aece5

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

doc/docs/modules/ROOT/pages/operations.adoc

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -63,6 +63,18 @@ The helm chart supports values for `additionalVolumes` and `additionalVolumeMoun
6363

6464
Use of additional volumes and mounts is not supported though, and in order to use this feature you must be very comfortable with filesystem basics in Kubernetes and Neo4j directory configuration.
6565

66+
## Transport Layer Security (TLS/SSL)
67+
68+
You can store public certificates in ConfigMaps and private keys in Kubernetes Secrets and use the helm chart's `additonalVolumes` and `additionalVolumeMounts` values to mount them into the Neo4j container.
69+
70+
The following neo4j config setting is required to support directly mounting certificates or keys from Kubernetes:
71+
72+
* `unsupported.dbms.ssl.system.ignore_dot_files=true`
73+
74+
Full details of SSL configuration can be found in the Neo4j operations manual. See the section "SSL Framework".
75+
76+
For an example of using certificates and keys stored in Kubernetes to secure internal traffic in a Neo4j Causal cluster please see the https://github.com/neo4j-contrib/neo4j-helm/blob/master/deployment-scenarios/cluster-internal-ssl/[cluster-internal-ssl deployment scenario].
77+
6678
## Fabric
6779

6880
In Neo4j 4.0+, https://neo4j.com/docs/operations-manual/current/fabric/introduction/[fabric] is a feature that can be enabled with regular configuration in `neo4j.conf`. All of the fabric configuration that is referenced in the manual can be done via custom ConfigMaps described in this documentation.

0 commit comments

Comments
 (0)