Skip to content

Commit

Permalink
fix neo4j volumes data mode
Browse files Browse the repository at this point in the history
  • Loading branch information
icemachined committed Nov 8, 2024
1 parent a2b79c5 commit db9e297
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions save-cloud-charts/save-cloud/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -201,9 +201,22 @@ neo4j:
memory: "2Gi"
volumes:
data:
mode: selector
selector:
# REQUIRED: specify a volume mode to use for data
# Valid values are share|selector|defaultStorageClass|volume|volumeClaimTemplate|dynamic
# To get up-and-running quickly, for development or testing, use "defaultStorageClass" for a dynamically provisioned volume of the default storage class.
mode: "volume"

# Only used if mode is set to "volume"
# Provide an explicit volume to use
volume:
# If set an init container (running as root) will be added that runs:
# `chown -R <securityContext.fsUser>:<securityContext.fsGroup>` AND `chmod -R g+rwx`
# on the volume. This is useful for some filesystems (e.g. NFS) where Kubernetes fsUser or fsGroup settings are not respected
setOwnerAndGroupWritableFilePermissions: false

# Example (using a specific Persistent Volume Claim)
persistentVolumeClaim:
claimName: data-neo4j-0
demo_cpg:
name: demo-cpg
profile: dev
Expand Down

0 comments on commit db9e297

Please sign in to comment.