From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: "Kevin Hilman" Subject: Re: Contribute to KernelCI in Kubernetes or Cloud In-Reply-To: References: <7hwo3g4irb.fsf@baylibre.com> <1621E054EEFB3FDC.11249@groups.io> <7hmu3r6ziu.fsf@baylibre.com> Date: Fri, 24 Jul 2020 11:48:13 -0700 Message-ID: <7hzh7o6976.fsf@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain List-ID: To: Aditya Srivastava Cc: kernelci@groups.io Aditya Srivastava writes: > On Thu, Jul 23, 2020 at 2:25 AM Kevin Hilman wrote: > >> Aditya Srivastava writes: >> >> [...] >> >> > I had one concern though, in the jinja2 file[1] the way args are >> inputted, >> > Can't there be a way to create a config file or something to use instead >> of >> > writing that huge args part (which can be error prone) >> >> Yes, as Guillaume said, we need a way to use config files for the tools. >> >> However, if we go this route, how do you pass the config file to the k8s >> job? So far, I only know how to start containers with >> arguments/parameters passed in env variables. >> >> Kevin >> > > Hi kevin, > You can create a persistent volume and mount the file in the pod. > I can show you an example of how it's done... I know about persistent volumes, but how do you push files to the k8s cluster so they show up in your volume? In your example, how does /root/PAG_K8S/prometheus get populated? Kevin