LWN: Comments on "KubeCon EU 2016, part 1: Kubernetes 1.2" https://lwn.net/Articles/680833/ This is a special feed containing comments posted to the individual LWN article titled "KubeCon EU 2016, part 1: Kubernetes 1.2". en-us Wed, 29 Oct 2025 08:34:58 +0000 Wed, 29 Oct 2025 08:34:58 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net KubeCon EU 2016, part 1: Kubernetes 1.2 https://lwn.net/Articles/681911/ https://lwn.net/Articles/681911/ ibukanov <div class="FormattedComment"> Yes, it became so natural for me to include a startup script with the image that generates config based on environment variables before starting the main service. It works but when the config is complex that turns the environment into very awkward mini-language that requires own maintenance, documentation etc. It is so much better to pass the config directly in its natural language.<br> </div> Thu, 31 Mar 2016 07:37:10 +0000 KubeCon EU 2016, part 1: Kubernetes 1.2 https://lwn.net/Articles/681836/ https://lwn.net/Articles/681836/ jberkus <div class="FormattedComment"> I don't really know the history of it, but from the start there was a lot of emphasis both in Docker and in Kubernetes placed on use of environment variables. I think that kept folks from thinking of other solutions, at first. <br> </div> Wed, 30 Mar 2016 23:12:17 +0000 KubeCon EU 2016, part 1: Kubernetes 1.2 https://lwn.net/Articles/681625/ https://lwn.net/Articles/681625/ ibukanov <div class="FormattedComment"> I wonder why it took so long to come up with something like ConfigMap. With docker some images assume that the configuration is passed like in -v host-path:/etc/service/config. It works but the drawback is that host-path must present and maintained on the host complicating deployment. It is nice that Kubernetes now takes care of those complications.<br> </div> Tue, 29 Mar 2016 13:47:09 +0000