Configure the Kuma CNI
In order for traffic to flow through the Kuma data plane, all inbound and outbound traffic for a service needs to go through its data plane proxy. The recommended way of accomplishing this is via transparent proxying .
On Kubernetes it’s handled automatically by default with the
kuma-init, but this container requires certain privileges.
Another option is to use the Kuma CNI. This frees every
Pod in the mesh from requiring said privileges, which can make security compliance easier.
DaemonSet itself requires elevated privileges because it
writes executables to the host filesystem as
Kuma CNI applies
NetworkAttachmentDefinitions to applications in any namespace with
NetworkAttachmentDefinitions to applications not in a Mesh, add the label
kuma.io/sidecar-injection with the value
disabled to the namespace.
Below are the details of how to set up Kuma CNI in different environments using both
- K3D with Flannel
- Azure Overlay
- AWS - EKS
- Google - GKE
- OpenShift 3.11
- OpenShift 4
kumactl install control-plane \ --set "cni.enabled=true" \ --set "cni.chained=true" \ --set "cni.netDir=/etc/cni/net.d" \ --set "cni.binDir=/opt/cni/bin" \ --set "cni.confName=05-cilium.conflist" \ | kubectl apply -f -
For Cilium versions < 1.14 you should use
cni.confName=05-cilium.conf as this has changed
for version starting from Cilium 1.14.
Kuma CNI taint controller
To prevent a race condition described in this issue a new controller was implemented.
The controller will taint a node with
NoSchedule taint to prevent scheduling before the CNI DaemonSet is running and ready.
Once the CNI DaemonSet is running and ready it will remove the taint and allow other pods to be scheduled into the node.
To disable the taint controller use the following env variable:
Merbridge CNI with eBPF
To install merbridge CNI with eBPF append the following options to the command from installation:
To use Merbridge CNI with eBPF your environment has to use
Kernel >= 5.7
--set ... \ --set "cni.enabled=true" \ --set "experimental.ebpf.enabled=true"
Kuma CNI logs
Logs of the are available via
eBPF CNI currently doesn’t have support for exposing its logs.