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.
On Friday, August 12, 2016 at 5:59:01 PM UTC+2, Rodrigo Campos wrote: > > On Fri, Aug 12, 2016 at 07:11:40AM -0700, kay ru wrote: > > For example PostgreSQL. Shall I use jobs to restore DB backup or deal > with > > the `/docker-entrypoint-initdb.d/`? > > I'd use a job that just connects to the database already running in some > other > pod or outside k8s. > > > If use `/docker-entrypoint-initdb.d/`, how can I deal with the `Bound` > > status for the `persistentvolumes` and `persistentvolumeclaims`? > > The volume will be mounted when a pod starts that use it, no need to deal > with > anything. If it's started, it's there. > -- 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.
