There are many use-cases to set additional env vars, e.g.
for setting HTTP_PROXY, as in environments with restricted networks, pods might need to have a proxy to be able to access the internet (or for any other reason which they want to set proxy)
for setting GOMAXPROCS as pods with low resources on large k8s nodes, get GOMAXPROCS == number of cores on nodes which causes cpu throttling issues. Users can manually set this to a lower value (e.g. number of cores in cpu.request)
In our use-case we need to set both, I think it is great if anyone can add this extra vars for their use-case instead of hard-coding it (it's also a common good practice in many official helm charts to allow customization)
This is fully backward compatible and doesn't change anything on existing deployments.
There are many use-cases to set additional env vars, e.g.
for setting HTTP_PROXY, as in environments with restricted networks, pods might need to have a proxy to be able to access the internet (or for any other reason which they want to set proxy)
for setting GOMAXPROCS as pods with low resources on large k8s nodes, get GOMAXPROCS == number of cores on nodes which causes cpu throttling issues. Users can manually set this to a lower value (e.g. number of cores in cpu.request)
In our use-case we need to set both, I think it is great if anyone can add this extra vars for their use-case instead of hard-coding it (it's also a common good practice in many official helm charts to allow customization)
This is fully backward compatible and doesn't change anything on existing deployments.