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 Kubernetes cluster on my local dev environment. > It's been a pretty magical experience so far, but I have a few questions > about config files as I'm getting ready to deploy to production. > > My main concern boils down to: is there any form of indirection for > specifying configuration in development vs. production? For example, I use > a private registry in dev (local) and prod, and in each environment I want > it to pull from the correct registry. I could just keep the same URL and > use /etc/hosts to redirect the dev registry to the local one, but I feel > like that's a weak solution. Another example would be the command I run for > a container in dev and prod are different (e.g. "--dev --log-to-console" vs > "--prod --log-to-file"). Again, I could probably get away with using > configmaps w/ environmental variables to hold the entire command and > interpolating it into the container command, but it feels kind of janky to > do that. > > If I recall correctly, there was some proposal for a Kubernetes templating > system for the configurations themselves, but that's not a hard feature yet. > > My solution for now is to create one configuration for dev and one for > production to account, each pointing to the correct registry. But a large > chunk of the files are the same, and I have to make sure everything else is > consistent. > > Have you guys dealt with this and if so, could you offer some suggestions > on how you tackled it? > > -- 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.
