Skip to content
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

Closed
1 task done
saturnism opened this issue Feb 11, 2017 · 6 comments
Closed
1 task done

Kubernetes descriptors to use dynamic volume provisioning #5173

saturnism opened this issue Feb 11, 2017 · 6 comments
Assignees
Milestone

Comments

@saturnism
Copy link
Member

saturnism commented Feb 11, 2017

  • Please follow the issue template below for bug reports and feature requests.
  • Tickets opened without any of these informations will be closed without any explanation.
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 directory

Irrelevant

Browsers and Operating System

All browsers/OS.

  • Checking this box is mandatory (this is just to show you read everything)
@saturnism saturnism changed the title Kubernetes descriptors to use automatic volume provisioning Kubernetes descriptors to use dynamic volume provisioning Feb 11, 2017
@pascalgrimaud
Copy link
Member

@PierreBesson : as you already use volumes for registry and consul, could you have a look to this ticket plz ?

@PierreBesson PierreBesson self-assigned this Feb 14, 2017
@PierreBesson
Copy link
Contributor

Yes of course.

@jdubois
Copy link
Member

jdubois commented Apr 27, 2017

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

@xetys
Copy link
Member

xetys commented May 2, 2017

I think I can cover this

@deepu105
Copy link
Member

deepu105 commented May 4, 2017

@xetys if this is included in #5603 please close this

@jdubois
Copy link
Member

jdubois commented May 22, 2017

Looks like this is being done in #5603 and this has been opened for way too long, so I'm closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants