Skip to content

Conversation

@solsson
Copy link
Contributor

@solsson solsson commented Aug 3, 2017

... or should we switch back to manually provisioned volumes, and find some other way to deal with multiple zones.

@solsson solsson force-pushed the persistent-volumes-retain branch from fe388a3 to b3ac6b7 Compare August 3, 2017 13:29
@solsson solsson changed the title Can dynamically provisioned volumes be set to Retain by default? Set provisioned volumes to Retain by default Aug 4, 2017
@solsson
Copy link
Contributor Author

solsson commented Aug 4, 2017

Let's keep dynamically provisioned volumes. There's good progress in 1.8. Once we've got that we'll update #50.

@solsson solsson force-pushed the persistent-volumes-retain branch from fb80993 to c51ba21 Compare August 4, 2017 05:39
@solsson solsson force-pushed the persistent-volumes-retain branch 3 times, most recently from 8e4fcdf to ae64d91 Compare August 8, 2017 10:44
@solsson solsson force-pushed the persistent-volumes-retain branch from ae64d91 to 4d3754d Compare August 8, 2017 10:45
@solsson solsson merged commit 4d3754d into master Aug 8, 2017
@solsson
Copy link
Contributor Author

solsson commented Aug 8, 2017

Actually I wanted to keep this PR open, while merging the README change to master, but github did the close. Let's remember to revisit this with Kubernetes 1.8.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants