Skip to content
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.

Support persistent storage for InfluxDB backend. #132

Closed
vishh opened this issue Feb 25, 2015 · 5 comments
Closed

Support persistent storage for InfluxDB backend. #132

vishh opened this issue Feb 25, 2015 · 5 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@vishh
Copy link
Contributor

vishh commented Feb 25, 2015

As of now InfluxDB pod uses local storage.

@pires
Copy link

pires commented Feb 26, 2015

+1

@vishh vishh added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Mar 21, 2015
@vishh
Copy link
Contributor Author

vishh commented Mar 28, 2015

Excepting local disk none of the existing Storage solutions in kubernetes works for all the users. I am thinking the best way to address this issue is to provide a cookbook of storage recipes in the repo and make the users choose one based on their deployment.
We can simplify this by having a deployment binary with simple flags.
Any thoughts @pires ?

@vishh vishh added this to the Kubernetes v1.0 milestone Mar 28, 2015
@jimmidyson
Copy link
Contributor

I think by default we should be using an empty-dir volume, but as we're seeing with lots of things this is deployment/implementation specific. A deployment binary might be a good idea, but we really need this to be in the influxdb manifest at the very least.

@pires
Copy link

pires commented Mar 28, 2015

I agree with @jimmidyson. I think it's up to the user to adopt whatever storage strategy he/she is more comfortable with. In the end, I'd really like to see something like flocker coming into Kubernetes, but right now it's too early to decide on an approach other than empty-dir.

@piosz
Copy link
Contributor

piosz commented Jun 21, 2016

closing in favor of #1197

@piosz piosz closed this as completed Jun 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

4 participants