Skip to content

dropping all capabilities of containerSecurityContext (#1729) #1730

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 19, 2024
Merged

dropping all capabilities of containerSecurityContext (#1729) #1730

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions modules/ROOT/pages/kubernetes/accessing-neo4j-ingress.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,7 @@ reverseProxy:
runAsUser: 7474
runAsGroup: 7474
capabilities:
drop:
- all
drop: [ "ALL" ]

podSecurityContext:
runAsNonRoot: true
Expand Down
2 changes: 2 additions & 0 deletions modules/ROOT/pages/kubernetes/configuration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -591,6 +591,8 @@ containerSecurityContext:
runAsNonRoot: true
runAsUser: 7474
runAsGroup: 7474
capabilities:
drop: [ "ALL" ]

# Readiness probes are set to know when a container is ready to be used.
# Because Neo4j uses Java these values are large to distinguish between long Garbage Collection pauses (which don't require a restart) and an actual failure.
Expand Down