Open diegoduarte-gb opened 5 months ago
Not a Helm chart issue. Transferred to the features-bugs repository per the guidelines here.
Hi @diegoduarte-gb . Kubecost single-cluster retention is based on the prometheus instance in the kubecost namespace's persistent volume and/or the backing files on the cost-model pod's persistent volume. Were either of these recreated during the upgrade process?
Kubecost Helm Chart Version
1.98
Kubernetes Version
1.25
Kubernetes Platform
EKS
Description
Hello folks!
After upgrading our EKS cluster to the 1.25, we noticed our kubecost stopped to work, due to some deprecations in the PSP features (as stated here https://github.com/kubecost/cost-analyzer-helm-chart/issues/1773#issuecomment-1299327504)
After some days research, we found that workaround and we decided to apply it. It worked, as expected and Kubecost is now back online.
However, we noticed that we lost our old metrics, and we got only new metrics from today and on. Checking the kubecost logs, I found the following in the logs (pasted in the log part)
After considering this, maybe our data is still here and somehow is not being read, or do we had another issue and we lost it, aftter pushing the helm chart with the updates to Argo?
thanks
Steps to reproduce
Expected behavior
The old metrics existing in the console
Impact
big - finops cant get any value from it
Screenshots
Logs
Slack discussion
No response
Troubleshooting