You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hi, it seems that log retention for our loki deployment stops working after we have redeployed loki a few times.
And all logs seems to be stored forever
I can't say for sure what triggers this, only that it has occured atleast 2-3 times now, when we have redeployed loki a few times with changed size of pvc and other misc changes, while reusing the same s3-buckets.
To Reproduce
deploy loki via helm-chart
delete loki deployment
redeploy loki with different settings, different size for pvc.s, replicas etc, while reusing same s3-buckets as previous deployments
Expected behavior
Loki log retentions still being applied to logs stored from later deployment, and current
Environment:
Infrastructure: company kubernetes cluster, local hitatchi s3 storage
Deployment tool: helm, argocd
Screenshots, Promtail config, or terminal output
Here is the configuration used, together with some loki log errors we can see.
loki_index_20075 seems to be the newest index stored in the s3 bucket
Describe the bug
Hi, it seems that log retention for our loki deployment stops working after we have redeployed loki a few times.
And all logs seems to be stored forever
I can't say for sure what triggers this, only that it has occured atleast 2-3 times now, when we have redeployed loki a few times with changed size of pvc and other misc changes, while reusing the same s3-buckets.
To Reproduce
Expected behavior
Loki log retentions still being applied to logs stored from later deployment, and current
Environment:
Screenshots, Promtail config, or terminal output
Here is the configuration used, together with some loki log errors we can see.
loki_index_20075 seems to be the newest index stored in the s3 bucket
The text was updated successfully, but these errors were encountered: