-
Notifications
You must be signed in to change notification settings - Fork 32
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
InfluxDB persistence after helm install #191
Comments
Yes you can do that. It would create a persistent volume and bind it to the influx pod. All data currently stored in the pod would be lost though since influx would need to restart to bind the volume. |
I think you should be able to do something like |
I've did what you said, but it's taking a long time to terminate the old pods and Grafana is not showing anything. Maybe it should be better to delete the release and reinstall it? The influxapi IP should be the same, right? It's a Service, it should discover its pods
|
If you are ok deleting the release and reinstalling then yeah I would try that. Ive recently been working on the charts and I have done several no persistence to persistence upgrades and didnt notice that issue. But that was on a branch of some stuff I was testing so it may not work that way in master. |
Could I enable InfluxDB persistence after
helm install deis/workflow
?I read the docs, but what would happen?
The text was updated successfully, but these errors were encountered: