You are browsing unreleased documentation.
See the latest documentation here.
Configure the Kong Mesh CNI
In order for traffic to flow through the Kong Mesh 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
On Kubernetes it’s handled automatically by default with the
kuma-init, but this container requires certain privileges.
Another option is to use the Kong Mesh 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
Install the CNI using either
kumactl or Helm
The default settings are tuned for OpenShift with Multus.
To use it in other environments, set the relevant configuration parameters.
Kong Mesh 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 Kong Mesh CNI in different environments using both
Kong Mesh 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 "kuma.cni.enabled=true" \
Kong Mesh CNI logs
Logs of the are available via
eBPF CNI currently doesn’t have support for exposing its logs.