I commented on this as well back when it was released - https://github.com/jenkinsci/kubernetes-plugin/pull/162#issuecomment-323867030

I can confirm a possible work around code early next week.

This is a very critical issue as we can't change the env vars of our pod template anymore.

What's going on with this one?  With these buttons being broken, the plugin appears very unprofessional.  A status update would be appreciated.

The status update is that there is no update.

As for the "unprofessional" appearance just a little reminder that this is open source and you are welcome to contribute a patch
You also have to realize that all the time used responding to "me too", "when is this going to be done" and "are we there yet" is time not going towards the fixing of the issues

Thanks

berni_ you can edit config.xml and add envVars by hand:

<envVars>
  <org.csanchez.jenkins.plugins.kubernetes.ContainerEnvVar>
    <key>FOO-KEY</key>
    <value>FOO-VALUE</value>
  </org.csanchez.jenkins.plugins.kubernetes.ContainerEnvVar>
  <org.csanchez.jenkins.plugins.kubernetes.ContainerEnvVar>
    <key>BAR-KEY</key>
    <value>BAR-VALUE</value>
  </org.csanchez.jenkins.plugins.kubernetes.ContainerEnvVar>
</envVars>

my jenkins is running outside of the cluster.. in my plugin also i am not getting envars.. it is showing empty then how can i add this config.xml and my doubt is i am running my job in jnlp-slave fine but its not running in my image which i am giving.. i named my container as jnlp then slave pod is showing offline in jenkins.... any idea???

Scheduled for 1.1.3