Increased SHM size by mounting a volume #3
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR increases shared memory for Nginx ingress controller in order to fix an issue we're currently having in live-1:
"modsecurity_rules" directive Failed to allocate shared memory (1): No space left on device in /tmp/nginx-cfg337881831:12572
The problem is Kubernetes only provides 64MB for shared memory [1] which doesn't look enough for our nginx-ingress-controllers (they're getting bigger every day). Some other applications (like PostgreSQL) are also implementing similar approaches.
[1] Easly checked as: