-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Kubernetes descriptors to use dynamic volume provisioning #5173
Comments
@PierreBesson : as you already use volumes for registry and consul, could you have a look to this ticket plz ? |
Yes of course. |
Hi guys, this has been opened for a long time - @PierreBesson or @saturnism would you be ready to work on this? Otherwise, unfortunately, I will close this, as we have too many bugs opened at the moment |
I think I can cover this |
Looks like this is being done in #5603 and this has been opened for way too long, so I'm closing this |
Overview of the issue
Currently, databases are mounting volumes from EmptyDir. This is convenient to get started with, but data will not survive restarts. Production deployment needs to be reconfigured.
Motivation for or Use Case
Make sure there is a good production deployment path.
Reproduce the error
yo jhipster:kubernetes
Related issues
N/A
Suggest a Fix
Use PVC & depend on dynamic volume provisioning (require StorageClass yaml)
See http://blog.kubernetes.io/2016/10/dynamic-provisioning-and-storage-in-kubernetes.html
JHipster Version(s)
v4.0.2
JHipster configuration
N/A
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryIrrelevant
Browsers and Operating System
All browsers/OS.
The text was updated successfully, but these errors were encountered: