Add insecure_registry config to crio.conf

[qlijin]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Support insecure-registries in the kubepray when the containter engine type is crio.

When the registry is insecur, there will be error msg:

Get \\\"https://x.x.x.x:5000/v2/\\\": http: server gave HTTP response to HTTPS client\"

Does this PR introduce a user-facing change?:

Add crio_insecure_registries option for specifying insecure_registries of crio

[k8s-ci-robot]

Hi @qlijin. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[MrFreezeex]

Thanks for your contribution!
/lgtm

[MrFreezeex]

/ok-to-test

[oomichi]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MrFreezeex, oomichi, qlijin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [oomichi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment