Hacker News new | past | comments | ask | show | jobs | submit login

> Right now, the deployment and configuration of an application is supposed to be separated but I feel they need to be just a bit more coupled.

You can dynamically configure kubernetes from within the cluster. You can either use client-go library or talk to the api server directly with rest. For other languages than Golang you may need to set up proxy server, but it's a single kubectl command.

So all the basic functionality is there, but IMO configuration should be separate if it is possible - having it in source control is nice. I only use dynamic api for scheduling kubernetes jobs.




What I imagine is something like the Procfile for Heroku.

The app decides what it runs and how, you can set configuration like domain, whether the application is public/private etc...

Once you push the application to the scheduler it will handle the rest.


Ah. Quite a lot of things you mention are possible by dynamically generating yaml config.

I wrote a blog post about using go kubernetes library to generate yaml : https://kozikow.com/2016/09/02/using-go-to-autogenerate-kube.... It's quite nice, even for static config IMO, due to type safety.

You can easily write golang binary that would ask user series of questions "what database would you like", "do you want public access", etc. and get yaml as output.


Yup. What I am saying is this: This should be a part of the core offering IMHO.

I think most people choose Heroku over rolling their own infrastructure simply because of the ease-of-use for getting started.


That's basically what Deis does. They use Kubernetes as the backbone and build a heroku layer on top.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: