Allow replacement of address prefixes for all images

[ErikJiang]

Signed-off-by: bo.jiang [email protected]

What type of PR is this?
/kind bug

What this PR does / why we need it:

first of all, a big thanks to @oomichi for this script, its functionality is very useful to me.
but I found in actual use that it doesn't seem to work properly for registering some private registry images to the local registry.

I think the reason is that the script only processes four types of image prefixes “k8s.gcr.io”, “gcr.io”, “docker.io”, and “quay.io”, and my image prefixes are not of these types.
I modified the script to support prefix processing for all images, and I added the settings to hosts to avoid "no such host" error.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Allow replacement of address prefixes for all images

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: ErikJiang / name: ERIK (7ecc4ed)

[k8s-ci-robot]

Welcome @ErikJiang!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. 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/kubespray 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 @ErikJiang. 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.

[cristicalin]

@ErikJiang please don't mark questions as resolved without answering them

[oomichi]

Thanks for improving the script.
Some comments in the pull request.

/cc @oomichi

[k8s-ci-robot]

@cyclinder: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-kubespray-yamllint

Use /test all to run all jobs.

In response to this:

/test kubespray-ci/pipeline Kubespray CI Pipeline Kubespray CI - packet_ubuntu20-calico-aio

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.

[cyclinder]

/test Kubespray CI - packet_ubuntu20-calico-aio
/test Kubespray CI Pipeline
/test kubespray-ci/pipeline

[k8s-ci-robot]

@cyclinder: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test pull-kubespray-yamllint

Use /test all to run all jobs.

In response to this:

/test Kubespray CI - packet_ubuntu20-calico-aio
/test Kubespray CI Pipeline
/test kubespray-ci/pipeline

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.

[k8s-ci-robot]

@ErikJiang: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test all

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.

[cyclinder]

/ok-to-test

[cyclinder]

/test all

[ErikJiang]

PTAL @cristicalin @oomichi

[cristicalin]

@ErikJiang the current CI errors can be fixed by rebasing your PR on the latest master branch.

[cyclinder]

/test all

[oomichi]

Thank you for updating this @ErikJiang
The change seems good for me.

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ErikJiang, oomichi

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

[cristicalin]

@ErikJiang 👍

/lgtm