Support Kata and Node Feature Discovery

[pixiake]

What does this PR do ？

Support installation of kata-container and node-feature-discovery using kubekey.

Kata Containers is an open source community working to build a secure container runtime with lightweight virtual machines that feel and perform like containers, but provide stronger workload isolation using hardware virtualization technology as a second layer of defense.

NodeFeatureDiscovery detects hardware features available on each node in a Kubernetes cluster, and advertises those features using node labels.

How to use ?

add spec.kubernetes.enableKata: true or spec.kubernetes.enableNodeFeatureDiscovery: true

• Kata will only take effect if the container manager uses containerd and cri-o.

example:

apiVersion: kubekey.kubesphere.io/v1alpha2
kind: Cluster
metadata:
  name: sample
spec:
  hosts:
  - {name: node1, address: 192.168.6.6, internalAddress: 192.168.6.6, password: Qcloud@123}
  roleGroups:
    etcd:
    - node1
    master:
    - node1
    worker:
    - node1
    ## Specify the node role as registry. Only one node can be set as registry.
    registry:
    - node1
  controlPlaneEndpoint:
    ##Internal loadbalancer for apiservers
    #internalLoadbalancer: haproxy

    domain: lb.kubesphere.local
    address: ""
    port: 6443
  kubernetes: 
    version: v1.21.5
    clusterName: cluster.local
    enableKata: true      # enable kata-containers，and specify `runtimeClassName: kata-qemu` in the Pod spec to create kata sandbox.
    enableNodeFeatureDiscovery: true  # enable node-feature-discovery
  network:
    plugin: calico
    kubePodsCIDR: 10.233.64.0/18
    kubeServiceCIDR: 10.233.0.0/18
    # multus support. https://github.com/k8snetworkplumbingwg/multus-cni
    enableMultusCNI: false
  registry:
    ## `docker registry` is used to create local registry by default.  
    ## `harbor` can be also set for type.
    # type: ""  
    privateRegistry: dockerhub.kubekey.local
    registryMirrors: []
    insecureRegistries: []
  addons: []

Signed-off-by: pixiake guofeng@yunify.com

[ks-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pixiake

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 [pixiake]

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

[24sama]

Are there only worker nodes that can use the kata containers?

[pixiake]

Yes, kata does not support host network, the control-plane components uses runc, so kata is not needed on the control-plane.

[24sama]

How do you think to use a struct to configure the kata and NodeFeatureDiscovery?
Just like:

Kata:
  enable: true
  moreOptions: xxxx
NodeFeatureDiscovery:
  enable: false

BTW, if we use this structure, in the golang struct, the type of the enable field we can set as *bool. This allows you to distinguish between "true", "false" and "not set".

[pixiake]

Good idea, I will update it.

[24sama]

/lgtm

[ks-ci-bot]

LGTM label has been added.

Git tree hash: 1bd18bd41e81629406f9a016518c052dade7500a

[24sama]

/cherrypick release-2.0

[ks-ci-bot]

@24sama: new pull request created: #1024

In response to this:

/cherrypick release-2.0

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.