Refactor master to control plane

[gooney152]

What type of PR is this?

/kind clean up
/wg-naming

What this PR does / why we need it:

refactor "master" to "controlplane"

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

@gooney152: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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]

@gooney152: The label(s) kind/clean, kind/up cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

/kind clean up
/wg-naming

What this PR does / why we need it:

refactor "master" to "controlplane"

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

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]

Hi @gooney152. Thanks for your PR.

I'm waiting for a kubernetes 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.

[gooney152]

/test

[k8s-ci-robot]

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

In response to this:

/test

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]

@gooney152: PR needs rebase.

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: gooney152
To complete the pull request process, please ask for approval from smarterclayton after the PR has been reviewed.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS
• api/OWNERS
• pkg/api/OWNERS
• pkg/apis/OWNERS
• staging/src/k8s.io/api/OWNERS
• test/conformance/testdata/OWNERS

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

[gooney152]

/retest

[gooney152]

/retest

[gooney152]

/retest

[k8s-ci-robot]

@gooney152: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-kind-ipv6	dc7f525	link	/test pull-kubernetes-e2e-kind-ipv6
pull-kubernetes-e2e-gce-100-performance	dc7f525	link	/test pull-kubernetes-e2e-gce-100-performance
pull-kubernetes-verify	dc7f525	link	/test pull-kubernetes-verify
pull-kubernetes-e2e-kind	dc7f525	link	/test pull-kubernetes-e2e-kind
pull-kubernetes-conformance-kind-ga-only-parallel	dc7f525	link	/test pull-kubernetes-conformance-kind-ga-only-parallel
pull-kubernetes-conformance-kind-ipv6-parallel	dc7f525	link	/test pull-kubernetes-conformance-kind-ipv6-parallel
pull-kubernetes-integration	dc7f525	link	/test pull-kubernetes-integration
pull-kubernetes-e2e-ubuntu-gce-network-policies	dc7f525	link	/test pull-kubernetes-e2e-ubuntu-gce-network-policies
pull-kubernetes-e2e-gci-gce-ingress	dc7f525	link	/test pull-kubernetes-e2e-gci-gce-ingress
pull-kubernetes-node-e2e-containerd	dc7f525	link	/test pull-kubernetes-node-e2e-containerd
pull-kubernetes-unit	dc7f525	link	/test pull-kubernetes-unit
pull-kubernetes-e2e-gce-ubuntu-containerd	dc7f525	link	/test pull-kubernetes-e2e-gce-ubuntu-containerd
pull-kubernetes-e2e-gce-csi-serial	dc7f525	link	/test pull-kubernetes-e2e-gce-csi-serial
pull-kubernetes-conformance-image-test	dc7f525	link	/test pull-kubernetes-conformance-image-test
pull-kubernetes-verify-govet-levee	dc7f525	link	/test pull-kubernetes-verify-govet-levee
pull-kubernetes-typecheck	dc7f525	link	/test pull-kubernetes-typecheck
pull-kubernetes-dependencies	dc7f525	link	/test pull-kubernetes-dependencies
pull-kubernetes-files-remake	dc7f525	link	/test pull-kubernetes-files-remake
pull-kubernetes-e2e-gce-storage-snapshot	dc7f525	link	/test pull-kubernetes-e2e-gce-storage-snapshot
pull-kubernetes-e2e-gce-storage-slow	dc7f525	link	/test pull-kubernetes-e2e-gce-storage-slow
check-dependency-stats	dc7f525	link	/test check-dependency-stats
pull-kubernetes-e2e-gce-alpha-features	dc7f525	link	/test pull-kubernetes-e2e-gce-alpha-features
pull-kubernetes-local-e2e	dc7f525	link	/test pull-kubernetes-local-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[caesarxuchao]

/triage accepted

[neolit123]

/remove-area kubeadm
/remove-sig cluster-lifecycle

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ritazh]

This PR at its current state is too large to review by each individual sigs. Closing this for now. @gooney152 Please separate this change into smaller PRs for each area. Thank you!

/close

[k8s-ci-robot]

@ritazh: Closed this PR.

In response to this:

This PR at its current state is too large to review by each individual sigs. Closing this for now. @gooney152 Please separate this change into smaller PRs for each area. Thank you!

/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.