Suggest to run reset.yml playbook for first-time users

[HoKim98]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind documentation

What this PR does / why we need it:

Users who are new to kubespray may fail to deploy the cluster because they are inexperienced. The problem is that if the cluster.yml playbook is re-executed after the first attempt fails, it fails again with a high probability even if the user-defined inventory is flawless.

This is because even if the cluster installation fails, useless configuration files such as /etc/kubernetes remain and kubespray tries to reuse them as much as possible. Therefore, when deploying for the first time, the users must execute the reset.yml playbook before deploying to delete all configuration files and packages that may conflict.

Unfortunately, README.md in the root directory is missing these important notices. I suggest running reset.yml in the Usage script to lower the chance of errors for first-time users. I expect this will also lower the possibility of issues due to lack of experience.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Suggest to run reset.yml playbook for first-time users

[k8s-ci-robot]

Hi @kerryeon. 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]

Hi @kerryeon, this looks reasonable to suggest this, thanks :D. Could you rebase your commit to retrigger the CI though?

[MrFreezeex]

Thanks!

/lgtm
/ok-to-test

[liupeng0518]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kerryeon, liupeng0518, MrFreezeex

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 [liupeng0518]

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