-
Notifications
You must be signed in to change notification settings - Fork 419
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
Available memroy in kubecost-cost-analyzer PVC is gradually decreasing #3701
Comments
@MageshSrinivasulu we'd expect this then to stabilize when you've hit your number of retention days. What's your retention number and how many days are you seeing in the UI now? |
@AjayTripathy I have set the etlDailyStoreDurationDays to 30 from its default configuration of 91 days. Can you please specify the helm configuration you are referring to? |
I had to clear some older files in the path |
@AjayTripathy Is this the one you are speaking about? |
yes. It will gradually increase until that time window then should stabilize. |
It has been more than 30 days since I made the changes. It keeps decreasing gradually. It is not getting stabilized |
Kubecost Helm Chart Version
2.4.0
Kubernetes Version
1.29
Kubernetes Platform
EKS
Description
Here is the graph that shows the available memory in the disk kubecost-cost-analyzer the trend in gradually trending lower. The sudden spike in availability is because I adjusted the etlDailyStoreDurationDays but it is not helping much still the memory slowly decreasing
is
Steps to reproduce
Deploy the latest helm. Integrate the Kubecost with your billing account and run it for some time. you will see the memory in PVC getting reduced gradually
Expected behavior
memory should be either getting freed up or available memory should not reduce gradually
Impact
Available memory in PVC keeps on getting reduced will soon run out of free space
Screenshots
Logs
No response
Slack discussion
https://kubecost.slack.com/archives/CLFV60Y90/p1728277157577009
Troubleshooting
The text was updated successfully, but these errors were encountered: