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.
Read more..

Elastic Beanstalk Elastic Beanstalk is Amazon’s answer to the easy management of container-based applications. EB trades functionality like service discovery, cross-node communication, and advanced scheduling for simplicity and ease-of-use. One often overlooked convenience provided by EB is its support for environment variables. Instead of breaking 12-factor app rules by encouraging the storage of environment variables in the repository (dev.yaml, staging.yaml, etc.) or creating workflow problems with a env.yaml per branch, EB does something better: an easily configurable key-value store for each environment you create.
Read more..

Managing secrets in Kubernetes is currently somewhat of a challenge. Kubernetes users have the Secret resource which works well to define secrets in the cluster, but where should secrets reside before they’re added to the cluster? One all-too-common pattern is to encrypt secrets and store them in a git repository for versioning and long-term storage. While this works, and one can argue that a git respository is nothing more than versioned abstract storage, the problem with this approach is not with git itself (or any other DVCS) but with the general use-case of DVCS’.
Read more..