Auto-generate Kubernetes ConfigMaps from Environr
Kubernetes ConfigMaps are a convenient way to encapsulate configuration values into a named resource and then access those values in your application as environment variables. Creating these resources, however, is typically a manual process, requiring either manually writing YAML or ingesting directories or files containing the values. Today, the most recent version of Environr’s CLI added support for a new output format: kubernetes-configmap. Invoking the CLI tool with the kubernetes-configmap outputter generates a Kubernetes ConfigMap with the same name as the Environr configuration set.
Ansible, Puppet, Chef: No thanks
I’m going to catch a lot of flak for this post, but I think it’s an important statement. In the most common cases, configuration management tools like Ansible, Puppet, and Chef encourage bad practices and should be avoided instead of celebrated. The only exception to this is managing an on-premise server fleet that can’t leverage software like Kubernetes, CoreOS, Apache Mesos or emulate an Infrastructure-as-a-Service platform like AWS or GCP.