remove k8s.io/kubernetes dependency from yurtctl join/reset

[rambohe-ch]

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 enhancement

What this PR does / why we need it:

Remove k8s.io/kubernetes dependency from yurtctl join and yurtctl reset.

1. feature update points:

• In order to reduce the complexity of yurtctl join command and integrate with sealer, join ControlPlane node feature is removed, so yurtctl join can only join cloud or edge worker node. and end user should use yurtctl init to install ControlPlane through sealer.
• yurtctl reset can only reset worker node that joined by yurtctl join command. if end user use yurtctl reset to reset other kind of nodes, the result maybe unknown.

2. yurtctl join command

• implementation update points:

  • dependency on kubeadm copied from k8s.io/kubernetes/cmd/kubeadm to github.com/openyurtio/openyurt/pkg/yurtctl/kubernetes. so KubeletConfiguration has been left.

  • command line parameter:

    • In order to reduce the complexity of input parameter, kubeadmapi.JoinConfiguration and kubeadmapi.InitConfiguration have been removed. only command line parameters are supported in yurtctl join.
    • add YurtJoinData interface.
    • apiServerAddress and token parameter for yurtctl join command
    • organizations parameter is added for adding customized Organizations info into yurthub client certificate.
    • node-labels parameter is added for adding customized labels for worker node.

• prepare phase(pkg/yurtctl/cmd/join/phases/prepage.go):

  • kubelet service conf file(/etc/systemd/system/kubelet.service.d/10-kubeadm.conf) is the same of cloud and edge worker node, so merge EdgeKubeletUnitConfig and CloudKubeletUnitConfig into KubeletUnitConfig
  • add /etc/kubernetes/kubelet.conf file preparation.
  • add /etc/kubernetes/pki/ca.crt file preparation.

• preflight phase(pkg/yurtctl/cmd/join/phases/preflight.go)

  • add /etc/kubernetes/kubelet.conf and /etc/kubernetes/pki/ca.crt file existing check
  • add pause and yurthub image pull check

• joinNode phase(pkg/yurtctl/cmd/join/phases/joinnode.go)

  • merge joinCloudNode/joindEdgeNode into joinNode because the join routine is the same except the WorkingMode parameter of yurthub.
  • openyurt.io/is-edge-worker label is added as kubelet command line parameter, so after kubelet startup, only CRISocket annotation is need to patch to node.
  • because kubelet use HTTP to connect yurthub, so rotate-certificates=faluse is added to kubelet command line parameter.
  • use templates.SubsituteTemplate to populate yurthub yaml, so the format of fields in YurthubTemplate are modified. for example: from __workingMode__ to {{.workingMode}}

• postCheck phase(pkg/yurtctl/cmd/join/phases/postcheck.go)

  • remove nodeLabel patch.

3. yurtctl reset command

• add resetData interface
• add preflight phase
• separate cleanfile phase into cleanupnode and cleanyurtfile phases.

Which issue(s) this PR fixes:

Fixes #671

Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

[openyurt-bot]

@rambohe-ch: 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 enhancement

What this PR does / why we need it:

Remove k8s.io/kubernetes dependency from yurtctl join and yurtctl reset.

Which issue(s) this PR fixes:

Fixes #671

Special notes for your reviewer:

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]

@adamzhoul @Peeknut @zyjhtangtang

[openyurt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[rambohe-ch]

@neo502721

[adamzhoul]

hi @rambohe-ch
I see this is a big and important update. we may take a while to fully understand.
can you have a simple description of what you did? so can help us understand more.
something like :

1. copy k8s code to dir yurtctl/kubernetes
2. merge joinCloudNode/joindEdgeNode into one( and I see you simplify the implantation can you have some introduction ？)
3. ...

PS: can some change in node can be implantation in node-servant? to make the update to kubelet/yurthub keep same.

very thanks.

[rambohe-ch]

hi @rambohe-ch I see this is a big and important update. we may take a while to fully understand. can you have a simple description of what you did? so can help us understand more. something like :

1. copy k8s code to dir yurtctl/kubernetes
2. merge joinCloudNode/joindEdgeNode into one( and I see you simplify the implantation can you have some introduction ？)
3. ...

PS: can some change in node can be implantation in node-servant? to make the update to kubelet/yurthub keep same.

very thanks.

@adamzhoul Thanks for your suggestions. i

hi @rambohe-ch I see this is a big and important update. we may take a while to fully understand. can you have a simple description of what you did? so can help us understand more. something like :

1. copy k8s code to dir yurtctl/kubernetes
2. merge joinCloudNode/joindEdgeNode into one( and I see you simplify the implantation can you have some introduction ？)
3. ...

PS: can some change in node can be implantation in node-servant? to make the update to kubelet/yurthub keep same.

very thanks.

@adamzhoul Thanks for your suggestions. i have updated the pull request messages.

[adamzhoul]

why fmt not klog?

[rambohe-ch]

fixed

[adamzhoul]

/lgtm