Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Possible memory leak #582

Closed
BitProcessor opened this issue Feb 2, 2021 · 2 comments
Closed

Possible memory leak #582

BitProcessor opened this issue Feb 2, 2021 · 2 comments
Labels
blocked needs validation In need of validation before further action bug Something isn't working wontfix This will not be worked on

Comments

@BitProcessor
Copy link

Hi,

I was looking at my flux namespace today to follow along a Helm release when I noticed the memory usage of the helm -operator container, roughly 2GB of RAM !

Screenshot 2021-02-02 at 13 38 53

Could this be a memory leak somewhere? I'm running version 1.2.0

@BitProcessor BitProcessor added blocked needs validation In need of validation before further action bug Something isn't working labels Feb 2, 2021
@BitProcessor
Copy link
Author

BitProcessor commented Feb 2, 2021

Update, checked on 2 other k8s clusters, found one using 1.5GB of RAM (91d up) and one using about 650MB of RAM (82d up). Seems related to #427 at first sight?

@pjbgf pjbgf added the wontfix This will not be worked on label Jul 26, 2022
@pjbgf
Copy link
Member

pjbgf commented Jul 26, 2022

Processing helm charts can be a resource intensive operation. Given that this project is now in "Migration and security support only", it is unlikely that any performance/resource consumption improvements will be merged.

For better resource optimisation you are better off migrating to Flux 2 and using helm-controller instead. That new controller has a caching feature which decreases the resource consumption throughout of its lifecycle.

More information about the Flux 2 transition timetable can be found at: https://fluxcd.io/docs/migration/timetable/.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocked needs validation In need of validation before further action bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants