We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sidecars are pretty limited in memory and CPU resources. We should increase the limits while keeping the current requests in place.
Proposal to add unlimited CPU to Vector, same request as before (100m CPU). config-builder from 256MB limit to 384MB limit, keeping the request same.
To avoid any OOM issues or potentially larger Vector processing to take forever.
The text was updated successfully, but these errors were encountered:
burmanm
Successfully merging a pull request may close this issue.
What is missing?
Sidecars are pretty limited in memory and CPU resources. We should increase the limits while keeping the current requests in place.
Proposal to add unlimited CPU to Vector, same request as before (100m CPU). config-builder from 256MB limit to 384MB limit, keeping the request same.
Why is this needed?
To avoid any OOM issues or potentially larger Vector processing to take forever.
The text was updated successfully, but these errors were encountered: