This was prompted largely by a move from Docker Compose, where we used env_file quite a bit. kenv will both create the Secret/ConfigMap resource as well as inject the env lookups into an existing Kubernetes resource (deployment, replicaset, daemonset, or replication controller). This allows us to keep our environment specific configuration alongside the app and just inject at deploy time.