I'm working in an environment where we push cloud instances of org.csanchez.jenkins.plugins.kubernetes.NonConfigurableKubernetesCloud, so that it can be configured centrally and the definition pushed to several Jenkins instance.

I found a problem with this approach: when defining a podTemplate in a pipeline, its definition gets added to the existing kubernetes cloud configuration. The cloud instance gets compared with the reference cloud instance and it is no longer equal, and so the cloud instance is replaced with the reference one. This interrupts (as far as I can see) the ongoing provisioning, and the dynamic templates get removed which prevents provisioning the corresponding agents.

The podTemplate keyword should avoid having side-effects on the kubernetes cloud configuration.