Move kubernetes/master to kubernetes/control-plane

[oomichi]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This is a small step to replace "master" with "control-plane" in Kubespray project.

Ref: #7157

Does this PR introduce a user-facing change?:

The role kubernetes/master has been renamed to kubernetes/control-plane.
If using the role kubernetes/master solely on previous Kubespray, it is necessary to update the specified role.

[floryut]

I think you can add a user facing change, as renaming a role can break some CI automation.
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, 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 [floryut]

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

[LuckySB]

how about rename tags: master in playbooks ?

[oomichi]

I think you can add a user facing change, as renaming a role can break some CI automation.
/approve

I see, I have updated the Does this PR introduce a user-facing change?: on this PR message.
Is it fine for us?

[oomichi]

how about rename tags: master in playbooks ?

That is a nice point.
I'd like to rename the tag on separated PR to avoid a single huge PR.

[floryut]

how about rename tags: master in playbooks ?

That is a nice point.
I'd like to rename the tag on separated PR to avoid a single huge PR.

Agreed there is a lot of work, nice to do it step by step

[champtar]

You can use rebase instead of squash ;)

[oomichi]

You can use rebase instead of squash ;)

I am not sure I understand the above point correctly.
If that means we need to put multiple commits in a single PR, that could make it hard to explain what is Does this PR introduce a user-facing change?: for users because we would need to write multiple things into Does this PR introduce a user-facing change?: in a single PR.

[champtar]

This is freeform text, you can put multiple lines ;)
BTW I think we should have the user impact/action needed in the commit message

[oomichi]

This is freeform text, you can put multiple lines ;)

It would be hard to know which release-note lines are related to commits if a single PR contains many commits which make release-note..

BTW I think we should have the user impact/action needed in the commit message

That is different manner from current Kubernetes community way and difficult to enforce contributors do that.
To generate release-note information, the release-notes tool gathers information from PR messages, not commit messages.

[floryut]

/cc @EppO

[EppO]

/lgtm
Thanks! I wanted to do that for a long time but never had time to do it.