Cilium CNI - Proxy mode ebpf

[clickersmudge]

Hi,
We read your article about Cillium CNI benefits (https://www.kubermatic.com/blog/cilium-cni-integration-in-kubermatic-kubernetes-platform/).

When creating KubeOne cluster we use this setting.

apiVersion: kubeone.k8c.io/v1beta2
kind: KubeOneCluster
versions:
  kubernetes: '1.24.7'
clusterNetwork:
  kubeProxy:
    skipInstallation: true
  cni:
    cilium:
      enableHubble: true
      kubeProxyReplacement: "strict"

cloudProvider:
  hetzner: {}
  external: true
addons:
  enable: true
  path: "./addons"
  addons:
    - name: "cluster-autoscaler"
    - name: "default-storage-class"
    - name: "unattended-upgrades"

However, when creating a cluster in KKP we do not see the "ebpf" option.

Only "iptables".

On user clustercCreated by KKP we see " kube-proxy-l26m2" pod:

kube-system            kube-proxy-l26m2                            1/1     Running   0          17m

Should it be like that?

[embik]

Hi @clickersmudge,

It's unfortunately not visible in your screenshot, but do you have konnectivity enabled? As per our CNI documentation, the epbf mode for Cilium is only available if konnectivity is enabled:

The most of the Cilium CNI features can be utilized when the ebpf Proxy Mode is used (Cilium kube-proxy-replacement is enabled). This can be done by selecting ebpf for Proxy Mode in the Cluster Network Configuration. Please note that this option is available only if Konnectivity is enabled.