Setting container cap limit doesn't work correctly without Jenkins restart. Once user set container cap limit configuration for given namespace, kubernetes plugin consider all pods/containers which are not started by the plugin (ideally it should query slave pods/container which are started by the plugin). It, in turn, results into invalid container cap count unless Jenkins get the restart.

After this we need to fix JENKINS-38260