Add kubespray-defaults role

[SimonGurney]

Fixes issues where an execution of remove-node.yml fails because a default value is not provided for proxy_disable_env

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 api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Fixes and issue where remove-node.yml execution fails
Which issue(s) this PR fixes:
Fixes #7801

Special notes for your reviewer:

Running the tests is beyond me so please can someone do this. I have tested execution by provisioning, scaling and removing an node and that works fine in my scenario.

Does this PR introduce a user-facing change?:
No

[k8s-ci-robot]

Welcome @SimonGurney!

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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: SimonGurney
To complete the pull request process, please assign mirwan after the PR has been reviewed.
You can assign the PR to them by writing /assign @mirwan in a comment when ready.

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

[oomichi]

@SimonGurney This pull request contains invalid-commit-message.
Please read https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#commit-message-guidelines to know what is invalid on the commit message and fix it.

[SimonGurney]

@SimonGurney This pull request contains invalid-commit-message.
Please read https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#commit-message-guidelines to know what is invalid on the commit message and fix it.

Apologies, I think thats sorted now. Had some issues with my commit verification but sorted it out now

[champtar]

This was fixed by #7729
/close

[k8s-ci-robot]

@champtar: Closed this PR.

In response to this:

This was fixed by #7729
/close

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.