Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
envFrom/ConfigMap not mapping environment variables to Docker container #230
I am using the
My deployment's pod template uses
The image running locally in Docker does not seem to receive the environment variables from this ConfigMap; it only receives the environment variables defined in the
λ kubectl apply -f ./test.yml configmap "my-configmap" configured deployment "my-deployment" configured λ kubectl logs my-deployment-4135175423-3rzj5 EXAMPLE_ENVFROM=foobar EXAMPLE_ENV=foobar
λ telepresence --swap-deployment my-deployment --docker-run alpine /bin/sh -c "env | grep EXAMPLE" Volumes are rooted at $TELEPRESENCE_ROOT. See http://www.telepresence.io/howto/volumes.html for details. EXAMPLE_ENV=foobar
OK, so I traced this to
Originally I used 2nd approach, and abandoned it because I was getting shell env variables... but they arguably was due to bad implementation on part. It seems like calling
If we run
added a commit
Jul 19, 2017
Sure -- we're transitioning to using Docker/Kubernetes, starting with development environments first. We're initially focusing on running everything locally within Minikube (we do not have many services, yet, so it all fits on our laptop at the moment). Most of our applications are PHP based, and at the moment I am planning to use the
Eventually I know we will outgrow a local Minikube cluster, and will have to move on to a remote development environment, which is where I can tell Telepresence will shine. Hopefully by using Telepresence earlier on, our team has flexibility with how and where it chooses to develop as our needs change.
I'm sure it will also find its way into our staging/production debugging workflows, once we move upward into those environments.