proposal to add subcommands init, join, reset for yurtctl.

[zyjhtangtang]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind design

What this PR does / why we need it:

This proposal add three subcommands init, join and reset for yurtctl. The subcommand init can create an all-in-one kubernetes cluster, simultaneously convert the kuberntes cluster to an OpenYurt cluster. The subcommand join is used to add a new node to an OpenYurt cluster, including cloud nodes and edge nodes. The subcommand reset can restore the node to the state before joining OpenYurt cluster.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

/assign @rambohe-ch @huangyuqi

Does this PR introduce a user-facing change?

other Note

[openyurt-bot]

@zyjhtangtang: GitHub didn't allow me to assign the following users: your_reviewer.

Note that only openyurtio members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind design

What this PR does / why we need it:

This proposal add three subcommands server, join and reset for yurtctl. The subcommand server can create an all-in-one kubernetes cluster, simultaneously convert the kuberntes cluster to an OpenYurt cluster. The subcommand join is used to add a new node to an OpenYurt cluster, including cloud nodes and edge nodes. The subcommand reset can restore the node to the state before joining OpenYurt cluster.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

/assign @rambohe-ch @huangyuqi

Does this PR introduce a user-facing change?

other Note

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.

[rambohe-ch]

how about rename the subcommand server to init, so the experience of yurtctl will be consistent with Kubeadm

[zyjhtangtang]

OK, I have renamed the subcommand server to init.

[yanyhui]

I think the 'join' subcommand should support multiple scenarios:

First, join node after executing 'server' subcommand;

Second, after the yurtctl convert to openyurt is executed on the original k8s cluster, the 'join' subcommand can be executed to access the new node;

Third, on the basis of the original k8s cluster, after manually installing openyurt, you can execute the 'join' subcommand to access the new node.

[rambohe-ch]

/lgtm

[rambohe-ch]

/approve

[openyurt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rambohe-ch, zyjhtangtang

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 [rambohe-ch]

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