We are testing and setting up the kubernetes plugin for use in a dev environment and working with the infrastructure teams to get proper certificate signing in place to ensure that we can use the remoting agents properly.

For example, we may have a dev instance of Jenkins without a properly signed or trusted certificate due to infrastructure teams not having the right DNS setup, etc.

Therefore, I propose to add an "-insecure" flag to the remoting jar file to provide support to bypass the certificate checks when communicating back the jenkins master. This is of course insecure and should ONLY be used for testing purposes.