-
Notifications
You must be signed in to change notification settings - Fork 772
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
Persistent Volumes #150
Labels
Comments
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Oct 5, 2016
Instead of creating emptydir, create PersistentVolumeClaim for docker-compose volumes by default Fixes kubernetes#150
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Oct 5, 2016
Instead of creating emptydir, create PersistentVolumeClaim for docker-compose volumes by default Fixes kubernetes#150
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Oct 5, 2016
Instead of creating emptydir, create PersistentVolumeClaim for docker-compose volumes by default Fixes kubernetes#150
surajssd
added a commit
to surajssd/kompose
that referenced
this issue
Oct 6, 2016
Instead of creating emptydir, create PersistentVolumeClaim for docker-compose volumes by default Fixes kubernetes#150
cab105
pushed a commit
to cab105/kompose
that referenced
this issue
Oct 27, 2016
Instead of creating emptydir, create PersistentVolumeClaim for docker-compose volumes by default Fixes kubernetes#150
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should start thinking about proper volume implementation.
Kompose should create PersistentVolumeClaims and use those for pod volumes, instead of using EmptyDir.
Real persistent volumes might also solve
volumes_from
problem (#131)The text was updated successfully, but these errors were encountered: