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
[kube-prometheus-stack] how to use persistent volumes instead of emptyDir #2816
Comments
Yeah I would like to know that as well please |
So I found the solution for the prometheus stack statefulset. You can either enable it in the values file
You can then reference this config file when installing or upgrading your helm chart like this Now I still have to figure out how to enable volume for the AlertManager. |
Here is config for alertmanager volume:
|
Thank you! I think this ticket can be marked as solved. |
Did this create a PVC for you? I can't find any in my cluster after applying the prometheusSpec.. |
Hi I also dont see any PVC created
and there is just one storageSpec: under the proper prometheusSpec: thank you |
Hi, when trying this way I have an error: failed to provision volume with StorageClass could not create volume in EC2: UnauthorizedOperation: You are not authorized to perform this operation . Directly, when I create a PVC I don't have this error? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Same here, no PVC created after adding the volumeClaimTemplate spec. |
same from my side, I specify the following
and there is no pvc created after that |
Try this
In my case, It works. If you missed |
Hmm strange I have it like this and it does not . Do you think there could be conflicting statements in the [Other configs]?
|
Facing the same issue here (trying to use persistent volumes for prometheus / alertmanager) |
I had the same issue. Found these two issues #563 and #655 and am now good. I'm using kube-prometheus-stack-45.29.0 helm chart. and below are relevant part of my-values
adding metadata name under volumeClaimTemplate: was needed for me becuase of the name too long issue/bug
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
i have a suspicion: I saw that this solution worked only on installing a chart. If you wanted to upgrade it was ignored. i guess the prometheus operator can not handle the migration of one storage (empty dir is the default i guess) to another one and therefore ignores it, because otherwise the data would be just lost. I do not know if there is a flag to or so to force this change but that could be the solution? |
Facing Same Issue |
Why not made just a parameter |
Because Storage is a complex topic and there's no one size fits all like solution (for example Storage Classes and Disk Sizes). |
This definitely looks like a bug. I tried installing 55.4.1 and the prometheus PVC would not get created no matter what I tried. I started successively taking lower releases (jumping several at a time), and it finally worked when I tried 48.5.0. So the bug was introduced somewhere between the two versions. |
Thank you for the hint, tried with version 55.7.1, but no pvc where created where as with version 48.5.0 it worked. |
Hello, I am also getting an error. prometheus: alertmanager: pods and statefulset are in pending state ..no pv, pvc pending |
I tried your yaml but it says pvc pending..it didn't work |
This is still in an issue in the latest version 56.16.0. |
Hey fellows, i would like to use persistent volumes instead of emptyDir(by default) config, does anybody how to do that?
i would really appreciate an example, getting confused with pv creation and also the pvc
The text was updated successfully, but these errors were encountered: