Has the name of an ENV var to be unique in the deployment defenition or in the . . .

Kubernetes-Slack Discussions
#1

Chris Bischoff:
Has the name of an ENV var to be unique in the deployment defenition or in the whole namespace? I tried to have two deployments with the same envvars names but with different values. But it seems to be a problem if i try to upgrade the deployment. The initial deployment works but updating not

#2

Sohaib Ahmed:
for example

env:

  • name: API_URL
    from configMap
  • name: API_URL
    from secretConfig

you question is related to above?

#3

Chris Bischoff:
More like:

#4

Chris Bischoff:
env:

  • name: API_URL1
    value: test1
  • name: API_URL2
    value: test1
#5

Chris Bischoff:
but to have the same in a second pod defenition or deployement with the the same names again but with different values

#6

Daz Mac:
The pod (metadata.name) or deployment (metadata.name)names cannot be the same within the same namespace.

The env names and values can be the same (or different) in each pod or deployment definition

#7

Chris Bischoff:
Ok THX than this is not my global design problem and I have to figure out why my deployment gets deployed but when i upgrade one of the env vars helm throws Error: UPGRADE FAILED The order in patch list: doesn’t match $setElementOrder list:

#8

Chris Bischoff:
Found the issue. Duplicate entries in long List of env vars. The helm linter is very useless in even simple cases … THX