same issue with 1.25.3.
Why we need envs with same keys? Can we delete same keys automatically?
The warning may ignored, then next time, I delete this dulplicate key, but kubernetes delete all envs(with same keys), this will lead to serious accidents.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
Just want to leave another workaround here that worked in our case, maybe it helps someone else.
If you have a duplicate ENV_VAR
and want to remove one of them, and (this is important and may or may not be the case for you) your container doesn't care about the casing of the variable name, so can remove one of the variables and change the casing of the other one.
Since Kubernetes considers ENV_VAR
and Env_Var
to be different things, this will circumvent the problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.
#125932 is currently being tracked as the long-term solution
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are on a team that was mentioned.