Add docs for 'setting up your first cluster'

[Svendegroote91]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
By providing a hands-on step-by-step example, people will get familiar Kubespray more easily.

Which issue(s) this PR fixes:
Fixes #6543

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

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. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @Svendegroote91!

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 @Svendegroote91. 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.

[floryut]

@Svendegroote91 Thank you for the PR, could you please check CLA ?
Also please take a look at markdown and yaml linters

[floryut]

/ok-to-test

[Svendegroote91]

@Svendegroote91 Thank you for the PR, could you please check CLA ?
Also please take a look at markdown and yaml linters

Working on that :-)

[Svendegroote91]

User updated for CLA

[hafe]

Would it be possible to use/change the existing sample inventory? This PR contains yet another sample inventory to maintain

[Svendegroote91]

Would it be possible to use/change the existing sample inventory? This PR contains yet another sample inventory to maintain

You mean the current sample inventory.ini? I would propose to change that file since the general documentation refers to yaml files whilst this is still .ini, or would that have impact on other parts of the code that leverage this sample inventory file?

[hafe]

To me it seems very abundant and overwhelming to add all those variables that already should have decent default values in the roles. Why not just add deviations from default values?

[Svendegroote91]

I removed the extra files and mentioned the deviations in text.

[Svendegroote91]

Any tip on the failing pipeline step?
It was not failing before, so I might have been unlucky this time?
It would surprise me if a markdown file would fail the actual code and build tests.

fatal: [instance-2]: FAILED! => {"attempts": 10, "changed": true, "cmd": "/usr/local/bin/etcdctl member add etcd3 --peer-urls=https://172.30.72.46:2380", "delta": "0:00:00.041774", "end": "2020-08-19 13:04:36.620176", "msg": "non-zero return code", "rc": 1, "start": "2020-08-19 13:04:36.578402", "stderr": "{\"level\":\"warn\",\"ts\":\"2020-08-19T13:04:36.618Z\",\"caller\":\"clientv3/retry_interceptor.go:61\",\"msg\":\"retrying of unary invoker failed\",\"target\":\"endpoint://client-7a0017d4-0f47-4248-8330-bebfedb9a6f8/172.30.72.47:2379\",\"attempt\":0,\"error\":\"rpc error: code = FailedPrecondition desc = etcdserver: Peer URLs already exists\"}\nError: etcdserver: Peer URLs already exists", "stderr_lines": ["{\"level\":\"warn\",\"ts\":\"2020-08-19T13:04:36.618Z\",\"caller\":\"clientv3/retry_interceptor.go:61\",\"msg\":\"retrying of unary invoker failed\",\"target\":\"endpoint://client-7a0017d4-0f47-4248-8330-bebfedb9a6f8/172.30.72.47:2379\",\"attempt\":0,\"error\":\"rpc error: code = FailedPrecondition desc = etcdserver: Peer URLs already exists\"}", "Error: etcdserver: Peer URLs already exists"], "stdout": "", "stdout_lines": []}

[woopstar]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Svendegroote91, woopstar

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

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