kubekey icon indicating copy to clipboard operation
kubekey copied to clipboard

Install CNI as an optional feature while using containerd

Open x86cloud opened this issue 2 years ago • 3 comments

Your current KubeKey version

./kk create cluster --container-manage containerd

Describe this feature

using containerd as the container manager, Containerd official has provided CNI plugin in the package. cni plugin can be an optional feature.

Describe the solution you'd like

tools add an option like --skip-cni-install to skip cni installation

Additional information

No response

x86cloud avatar Feb 25 '22 08:02 x86cloud

I don't think we need the param --skip-cni-install, it will let the user confused.

liangyuanpeng avatar Feb 27 '22 08:02 liangyuanpeng

You can install the cluster using the kubekey config that sets up the .spec.networks.plugin as none and sets up addons to deploy your CNI plugin.

For example, the following is a kubekey config example:

network:
    plugin: none
addons:
  - name: calico
    namespace: kube-system
    sources: 
      yaml: 
        path: 
        - /mycluster/calico/calico.yaml

Links:

  1. https://github.com/kubesphere/kubekey/blob/master/docs/addons.md
  2. https://github.com/kubesphere/kubekey/blob/master/docs/config-example.md

24sama avatar Feb 28 '22 02:02 24sama

You can install the cluster using the kubekey config that sets up the .spec.networks.plugin as none and sets up addons to deploy your CNI plugin.

For example, the following is a kubekey config example:

network:
    plugin: none
addons:
  - name: calico
    namespace: kube-system
    sources: 
      yaml: 
        path: 
        - /mycluster/calico/calico.yaml

Links:

  1. https://github.com/kubesphere/kubekey/blob/master/docs/addons.md
  2. https://github.com/kubesphere/kubekey/blob/master/docs/config-example.md

You can install the cluster using the kubekey config that sets up the .spec.networks.plugin as none and sets up addons to deploy your CNI plugin.

For example, the following is a kubekey config example:

network:
    plugin: none
addons:
  - name: calico
    namespace: kube-system
    sources: 
      yaml: 
        path: 
        - /mycluster/calico/calico.yaml

Links:

  1. https://github.com/kubesphere/kubekey/blob/master/docs/addons.md
  2. https://github.com/kubesphere/kubekey/blob/master/docs/config-example.md

i mean kubecni,not network plugin. because containerd already provide cri-containerd-cni-1.6.0-linux-amd64.tar.gz option, so i think, if i am using containerd as cri. there is no longer need kubecni.

x86cloud avatar Feb 28 '22 02:02 x86cloud