Preventing nginx controller errors #81
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why are these changes needed?
As explained in the issues below, when nginx-ingress
worker-processesvalue is set toautoor is not set, which means it spawns as many processes as cores are detected. When there are many CPU cores, we can face the issue that the Ingress-controller "exited with fatal code 2 and cannot be respawned." This happens whenpid limitsis violated.Related issue number (if any).
kubernetes/ingress-nginx#6141
cri-o/cri-o#5779
Signed-off-by: Alexey Roytman roytman@il.ibm.com