Skip to content
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.

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

Raise ingress-nginx default backend limits #1070

Merged
merged 1 commit into from Feb 12, 2019

Conversation

jakolehm
Copy link
Contributor

It seems that new cri-o/runc might consume more memory on start.. and sometimes default-backend ends up in "cannot allocate memory" error.

@jakolehm jakolehm added the bug Something isn't working label Feb 12, 2019
@jakolehm jakolehm added this to the 2.2.1 milestone Feb 12, 2019
@jakolehm jakolehm merged commit 6fb8037 into master Feb 12, 2019
@jakolehm jakolehm deleted the fix/ingress-nginx-default-backend-limits branch February 12, 2019 14:01
@jakolehm jakolehm mentioned this pull request Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants