Guys, don't stick on cloud providers (there is a world when people don't use amazon, azure or gce, but use bare-metal). As for NFS or ceph, sometimes your app requires local storage for performance reasons.
Thanks for advises ;) On Saturday, August 13, 2016 at 6:28:05 PM UTC+2, Rodrigo Campos wrote: > > > > On Saturday, August 13, 2016, kay ru <kay....@gmail.com <javascript:>> > wrote: > >> The problem that I already use initdb.d to initialize the DB container. >> But in kuberentes it is an chicken-egg problem. You don't know where >> exactly local PersistentVolume will be initialized. So it looks like there >> are two ways to resolve that: 1) Use jobs to restore the backup 2) >> Implement selector for the `host_path` plugin. >> > > Why not use a volume from the cloud provider, NFS, cephfs or something > else? > > Using the host volume is not something you want, in general, if you want > persistent data to live longer than a pod. If the host crashes (or just > maintenance, kernel upgrade, etc.), then you can't start your db, or will > start without data etc. > > Using a persistent volume from your cloud provider you avoid this, is > usually with raid and that stuff, and can be attached to any host you have > available to run your container. > > Also, using NFS, or some other volume plugin will do the trick. > -- 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.
