Hi-- Any good solutions for job input and output? I'm running into the same problem and was looking at spinning up a temp minio (https://www.minio.io/) instance (without persistent store) or something along those lines, but simpler solutions would be nicer. Mostly the goal is to avoid having to separately clean up data/persistent storage afterwards.
On Monday, May 21, 2018 at 8:55:17 PM UTC-7, bimar...@google.com wrote: > > I am setting up a go application that will create jobs. For each job > execution, I need to pass a blob of parameter data into the job container, > and get a blob back out. I'd like to avoid a requirement for database > access in the job. > > Volumes seem awfully complicated, and, anyway, I don't see a > straightforward way to get a files on and off of a GCE PD volume. I suppose > I'm missing something simple, or that there's some other volume type that > would be more appropriate. > -- 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.
