Re: jep/213 "Configuration Storage API" vs SideCar

2018-10-01 Thread Jesse Glick
BTW could you move this thread to jenkins-cloud-native-...@googlegroups.com which is probably the right forum? -- 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

Re: jep/213 "Configuration Storage API" vs SideCar

2018-10-01 Thread Jesse Glick
On Mon, Oct 1, 2018 at 6:51 AM nicolas de loof wrote: > we just don't need to wait for a new jenkins-core release, this can be > adopted without delay. If I understand your proposal correctly, you suggest that a sidecar container fetch cloud-native configuration (say, K8S CRDs) as an

jep/213 "Configuration Storage API" vs SideCar

2018-10-01 Thread nicolas de loof
Hi, I've read JEP-213 proposal with lots of interest, IIUC there's no plan to change the configuration granularity (we still will have one configuration entry per legacy xml file) neither do we plan to change the data being