Yep, I've just tried it :) As a followup question:
If I run some DB as a Kubernetes pod (ignore for a second that it might not be recommended) - is it a good case to using hostPath volume so the data will persist even if the pod is killed? Thanks On Wednesday, June 29, 2016 at 5:32:30 PM UTC+3, Rodrigo Campos wrote: > > No, it won't. > > You can also try it, just docker kill or kubectl delete pod, and you can > check it :-) > > On Wednesday, June 29, 2016, Ori Popowski <[email protected] <javascript:>> > wrote: > >> Hi, >> >> If a replication controller contains an emptyDir volume and say, 3 >> replicas, and for some reason one of the pods was killed and spawned again >> by the replication controller on the same node: >> >> Will the data in that volume still exist? >> >> Thanks >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Containers at Google" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/google-containers. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
