On Fri, Jan 25, 2019 at 8:51 AM Tomasz Sęk <[email protected]> wrote: > We had a lot of issues when Kubernetes coudn't detach PVC after pod restart > and the new one coudn't be loaded.
I see. Thanks for clearing this up. >>> we have to run some jobs on master to configure it(apply groovy scripts, >>> restore/backup and seed jobs creation). > >> This seems inadvisable and is generally insecure. Better for these tasks to >> be externalized. > > encapsulati[ng] configuration tasks into jobs give view what is wrong with > configuration provided by user. Perhaps these tasks could be made into K8s batch jobs instead? > Maybe there is a solution where we can restrict which jobs can be run on > master? It is possible with some plugins and core extension points, but not currently well supported. See discussion in JENKINS-24513. If you can avoid it and run operator subtasks in separate pods, it would be better. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr32Qa%3DY56L9AypobWwkk%2B3UMbNO7uwzjoSp4936FLEtzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
