custom cni (disable flannel)

[mkmik]

According to https://docs.k3s.io/installation/network-options#custom-cni if we want to install a custom CNI, we need to pass --flannel-backend=none.

In order to do that, we need to surface the config in K3sServerConfig and in the relevant CRDs

type K3sServerConfig struct {
	DisableCloudController    bool     `json:"disable-cloud-controller,omitempty"`
	KubeAPIServerArgs         []string `json:"kube-apiserver-arg,omitempty"`
	KubeControllerManagerArgs []string `json:"kube-controller-manager-arg,omitempty"`
	TLSSan                    []string `json:"tls-san,omitempty"`
....
}

[zawachte]

sgtm

[ekarlso]

You can do this via the files section pretty easily:

    files:
    - content: |
        flannel-backend: none
      owner: root:root
      path: /etc/rancher/k3s/config.yaml.d/disable-flannel.yaml

[ekarlso]

I think we could probably simplify this though with a property so that we can drive these things a bit easier then having to hack it together via the files section.

flannelBackend: None
disableNetworkPolicy: true
disableKubeProxy: true

[dberardo-com]

is it possible to disable flannel on an already existing k3s cluster ? and then install another plugin, like calico ?