You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Reverse proxy Helm chart creates an HTTP server, which routes requests to either the Bolt reverse proxy or HTTP reverse proxy based on the request headers.
17
17
Upon receiving a response, the Bolt reverse proxy updates the response to replace the Bolt port with either `:80` or `:443`.
18
18
19
+
From version 5.17.0, the Reverse proxy Helm chart supports defining privilege and access control settings for a Container.
20
+
Make sure that you do not run Neo4j as a root user.
21
+
19
22
== Configuration options
20
23
21
24
To see all configurable options, run the following command:
@@ -36,8 +39,7 @@ fullnameOverride: ""
36
39
37
40
# Parameters for reverse proxy
38
41
reverseProxy:
39
-
image: "neo4j/helm-charts-reverse-proxy:5.12.0"
40
-
42
+
image: "neo4j/helm-charts-reverse-proxy:5.17.0"
41
43
# Name of the kubernetes service. This service should have the ports 7474 and 7687 open.
42
44
# This could be the admin service ex: "standalone-admin" or the loadbalancer service ex: "standalone" created via the neo4j helm chart
43
45
# serviceName , namespace , domain together will form the complete k8s service url. Ex: standalone-admin.default.svc.cluster.local
@@ -47,6 +49,24 @@ reverseProxy:
47
49
# default is set to cluster.local
48
50
domain: "cluster.local"
49
51
52
+
# securityContext defines privilege and access control settings for a Container. Making sure that we dont run Neo4j as root user.
53
+
containerSecurityContext:
54
+
allowPrivilegeEscalation: false
55
+
runAsNonRoot: true
56
+
runAsUser: 7474
57
+
runAsGroup: 7474
58
+
capabilities:
59
+
drop:
60
+
- all
61
+
62
+
podSecurityContext:
63
+
runAsNonRoot: true
64
+
runAsUser: 7474
65
+
runAsGroup: 7474
66
+
fsGroup: 7474
67
+
fsGroupChangePolicy: "Always"
68
+
69
+
50
70
# This assumes ingress-nginx controller or haproxy-ingress-controller is already installed in your kubernetes cluster.
51
71
# You can install ingress-nginx by following instructions on this link https://github.com/kubernetes/ingress-nginx/blob/main/docs/deploy/index.md#quick-start
52
72
# You can install haproxy-ingress by following instructions on this link https://haproxy-ingress.github.io/docs/getting-started/
0 commit comments