search

pulumi / pulumi-kubernetes-operator

A Kubernetes Operator that automates the deployment of Pulumi Stacks
Apache License 2.0
221 stars 55 forks source link

Possible memory leak #420

Closed skdltmxn closed 1 year ago

skdltmxn commented 1 year ago

What happened?

I see the memory consumption by the operator keeps increasing.
Attached capture shows memory usage graph for past week.
Considering there was no change for last four days, I don't understand why it's increasing.
Could there be any memory leak?

image

Expected Behavior

The memory consumption should stay consistent unless there is any reason.

Steps to reproduce

Run the operator with periodic reconcile enabled

Output of pulumi about

CLI
Version      3.46.0
Go Version   go1.19.2
Go Compiler  gc

Host
OS       debian
Version  11.5
Arch     x86_64

Pulumi locates its logs in /tmp by default

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

danielrbradley commented 1 year ago

Thanks for reporting this @skdltmxn

This looks like it'll likely be a tricky issue to reproduce, can you share any more details about your setup (code if possible). Have you managed to reproduce the issue in a smaller isolated environment?

skdltmxn commented 1 year ago

Hi, I've been monitoring memory usage since this report, and further graph seems pretty stable.

Let me close the issue for now and open again if I could really assure myself there's some problems.

danielrbradley commented 1 year ago

This also might have been resolved by https://github.com/pulumi/pulumi-kubernetes-operator/pull/407 which was related to a cache growth issue. The next release that goes out will include this. Do let us know if you continue to see issues after upgrading.