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

Python and Go init/sidecar containers being OOMKilled with default settings #3479

Open
jcreixell opened this issue Nov 20, 2024 · 0 comments

Comments

@jcreixell
Copy link
Contributor

jcreixell commented Nov 20, 2024

Component(s)

auto-instrumentation

Describe the issue you're reporting

The init/sidecar containers are being killed by kubernetes due to memory usage above the limits. This happens with python and go.

I am able to consistently reproduce the go OOMs with both k3d and kind:

kind

Interestingly, the python OOMs only happen with k3d, not kind.

Screenshot from 2024-11-20 18-33-10

Screenshot from 2024-11-20 18-33-55

I am using a standard setup following the README. For testing, I use the rolldice applications with their manual instrumentation code stripped out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant