<p dir="auto">Hi,</p>
<p dir="auto">We're using deployments on Kubernetes version 1.2.1.</p>
<p dir="auto">In order to update deployments we update the corresponding deployment.yml file and the run<br>
<code class="notranslate">kubectl apply -f deployment.yml</code></p>
<p dir="auto">Everything works well most of the time except for the case in which we add an environment variable to one of the containers on the deployment.yml.</p>
<p dir="auto">In that case we see that a new replica set is not created and the old pods keep on running.</p>
<p dir="auto">Deployment is defined in a json file with several environment varibles. Deployment is deployed using "kubectl apply -f deployment.json". Pods get most of the environment variables defined, but not all.</p>
<p dir="auto">Specifically, the variables defined in the deployment.json are named:<br>
<code class="notranslate">{ "name": "DB_HOSTS", "value": "10.0.0.1" }, { "name": "SLACK_ENDPOINT", "value": "ERRORNOT" }, { "name": "LACK_ENDPOINT", "value": "ERRORNOT" }, { "name": "SLACK", "value": "ERRORNOT" }, { "name": "CK_ENDPOINT", "value": "ERRORNOT" }, { "name": "ACK_ENDPOINT", "value": "ERRORNOT" }, { "name": "K_ENDPOINT", "value": "ERRORNOT" }, { "name": "CASSANDRA_LOGGING_LEVEL", "value": "ERROR" }, { "name": "ENABLE_GETIP", "value": "https://www.url.com" }</code></p>
<p dir="auto">the environment variables that appear in a pod are:</p>
<p dir="auto">`<br>
ENABLE_GETIP</p>
<p dir="auto">CASSANDRA_LOGGING_LEVEL</p>
<p dir="auto">K_ENDPOINT</p>
<p dir="auto">ACK_ENDPOINT</p>
<p dir="auto">CK_ENDPOINT</p>
<p dir="auto">DB_HOSTS<br>
`</p>
<p dir="auto">That is, ENV variables named "SLACK_ENDPOINT", "LACK_ENDPOINT" and "SLACK" never get passed on to the pods.</p>