Separate --insecure-skip-tls-verify flag into two separate flags

[DerDackel]

Possibly fixes #310

[googlebot]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again. If the bot doesn't comment, it means it doesn't think anything has changed.

[container-tools-bot]

Hi @DerDackel. Thanks for your PR.

I'm waiting for a GoogleContainerTools member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[googlebot]

CLAs look good, thanks!

[priyawadhwa]

Thanks for contributing! This looks good to me overall, could you also update the README to include these flags in the Additional Flags section?

[priyawadhwa]

Could we rename DockerInsecure to something which doesn't include Docker in the name, maybe InsecurePush?

[DerDackel]

Done and done. I took the liberty of adding a warning about their intended use to both flags.

[priyawadhwa]

Thanks! I think you just have to rebase against master and this should be good.

[dlorenc]

/lgtm

[priyawadhwa]

LGTM, thanks for fixing this!