Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Memory leak

See original GitHub issue

sentry-kubernetes on our two clusters leaks memory, at least memory usage has only gone up during a few weeks of usage:

We have RBAC enabled and given sentry-kubernetes’ service account the ClusterRole view.

As a workaround, we’ve now set the following resource requests/limits for the sentry-kubernetes container:

resources:
  requests:
    memory: 75Mi
    cpu: 5m
  limits:
    memory: 100Mi
    cpu: 30m

We expect these limits to restart the container every few days.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:10 (1 by maintainers)

Top GitHub Comments

7reactions

wichertcommented, Oct 22, 2019

FWIW I made another alternative: https://github.com/wichert/k8s-sentry . That means there are now three alternatives:

this version. Currently not really usable since it has this memory leak and isn’t actively maintained.
@stevelacy’s go-sentry-kubernetes. A small Go reporter without memory leak. This monitors pods for changes and reports those to Sentry. Includes very little information in error messages.
my k8s-sentry. Another small Go reporter. This uses the same approach as this project: it monitors events, and submits warning and errors events to Sentry. It includes a fair bit of information from events (object kind, namespace, component, event reason, event message, action taken, etc.). I might extend it to load fetch involved objects as well so it can add their labels and extra information as well (which would solve #13).

5reactions

stevelacycommented, Feb 21, 2019

I ended up creating a lightweight reporter in golang that uses 7-10mb ram total and reports pod failures: https://github.com/stevelacy/go-sentry-kubernetes