On Sun, Aug 14, 2016 at 12:29 AM, kay ru <kay.d...@gmail.com> wrote: > 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 advice ;) >
I agree with Rodrigo - even separate from using a Cloud, do NOT put a database on a single node. Either cluster your database, or use shared storage. Given your constraints, I think there are three options: - Use emptyDir - this uses local storage, but is empty every time a container is rescheduled. - Use hostDir - this uses local storage, and persists across container restarts. HOWEVER, if your container reschedules to a new host, this will not have any content in the directory. - Label a single node, schedule your container to a node to that label, and use hostDir PetSet (in alpha) will solve this within O(months). -- 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.
