[kubernetes-users] Re: Abstracting environmental differences in config files

2017-03-09 Thread Warren Strange
Helm works nicely for this. You can template out things like the registry, image names, etc., and then have a small values.yaml file that sets the values for the target platform. On Wednesday, March 8, 2017 at 11:56:45 PM UTC-7, ag...@jantox.com wrote: > > I am currently running a

Re: [kubernetes-users] Abstracting environmental differences in config files

2017-03-09 Thread Jay Vyas
The problem of unifying dev and prod is always tricky because configuration differs in subtle ways, but I think the idiom that we seem to see is: 1) Outside/before kube starts: Tools like ansible and salt and so on are generally designed to separate config from deployment. Those tools will ssh

Re: [kubernetes-users] Abstracting environmental differences in config files

2017-03-09 Thread Rodrigo Campos
We use several configmaps per pod, and to create some we have like 3 folders: all, staging, production. And we create with kubectl create configmaps asd --from-file=all --from-file=staging And then it's quite easy to share things. Although we try to avoid things like that as much as possible. We