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

During cert exporter bootup, cert-exporter consuming 143+ MB of memory #137

Open
dsnr-coder opened this issue Jul 18, 2023 · 1 comment
Open

Comments

@dsnr-coder
Copy link

Hi,

In the past few helm installations of cert exporter, we could see that cert exporter memory spike is happening and consuming memory around 143+ MB.

We have not modified resource limits that were present in cert-exporter helm chart. With the below resource limits, helm installations where going through since for sometime, all of a sudden, since past 5 installations, intermittently we started observing that cert-exporter is going into CrashLoopBackOff state, due to OOMKilled error.

When I check Grafana for cert exporter memory usage, I could see that for 3 seconds cert exporter has consumed 143+ MB, after 3 seconds, it has settled down, and not went beyond 90MB of memory.

  resources:
     limits:
       cpu: 100m
       memory: 128Mi
     requests:
       cpu: 100m
       memory: 128Mi

I had looked into the logs of cert-exporter, I could see that periodicSecretChecker.go took around 8 seconds , when periodicSecretChecker is getting executed, cert-exporter is consuming more memory.
image

Please find the screenshot from Grafana below
image

I would appreciate if you could please throw some light on guidance on how to troubleshoot and fix the issue.

@joe-elliott
Copy link
Owner

If you can profile memory and provide a flamegraph that would help identify memory usage. Other useful information would be the kind and number of secrets you are looking for.

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

No branches or pull requests

2 participants