Thanks for these suggestions! But do these solutions use persistent disk? In my case the persistent disk is a necessary requirement because in certain rare situations the pods restart. Therefore it is necessary to use a persistent disk so that the code does not change in case of reboot..
Just to clarify the scenario under analysis: - the image that I'm using is a debian with svn installed and configured - so inside the image there is all my project code (besides apache, php, etc) - after a deploy I could execute a 'svn update' on every pod (using a multi-terminals app like Terminator) but the problem is that if a pod restarts, the code will return to the original revision when the image was created So I'm searching a solution where I could use a daemonset configuration with a hostPath section where to indicate, in some way, a persistent disk (previously created) and the path where to mount it -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
