deploy local registry with ssl

[kriegmaster56]

Due to kubernetes not allowing plain http image registry,

i modify the script to generate a self signed certificate and deploy the registry with it. The script also configure kubernetes to use the registry with ssl enabled.

the registry is still available from the host using the same address localhost:5001 to push images.

[linux-foundation-easycla]

• ✅login: kriegmaster56 / (60668b6)
• ✅login: kriegmaster56 / (60668b6, 8a5de3f)
• ✅login: kriegmaster56 / (60668b6, 8a5de3f, 2ac047e)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kriegmaster56
Once this PR has been reviewed and has the lgtm label, please assign bentheelder for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

Welcome @kriegmaster56!

It looks like this is your first PR to kubernetes-sigs/kind 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kind has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @kriegmaster56. 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-sigs/prow repository.

[BenTheElder]

Due to kubernetes not allowing plain http image registry,

Huh? Kubernetes does not talk to a registry, only the container runtime does.

And we control the container runtime.

[BenTheElder]

I don't think we want to make the demo script more complicated for a non-essential feature, this is only used locally for development anyhow.

You can of course make more complicated versions of it for personal use, but I have not seen this failing to work in any use case yet.