Configure UCT-C Controller and TAP through GigaVUE-FM

This section describes how to configure UCT-C through GigaVUE-FM GUI. Refer to the following section for details.

Exclusion Criteria

Host Network Enabled - The UCT-C introduces support for tapping Host Network Enabled pods. By default, this check box is selected (i.e.) you are excluding the host network enabled pods.

When you want to monitor the pod, clear the Host Network Enabled checkbox. A warning message appears and requires your confirmation to proceed with tapping pods with Host Network Enabled.

Notes:
  • Worker Node must have cgroup version 2 to support the Host Network Enabled feature.

  • If the Worker Node has cgroup version 1, the policy deployment status for pod will show an error message.

  • When tapping Host Network enabled pods, tapped traffic is sent to user space for tunneling. It uses performance buffers, requiring more memory. To accommodate this, increase the memory request/limit to atleast 1GB for UCT-C taps.

Identify the cgroup Version on the Worker Node

To check which cgroup version your distribution uses, there are two ways:

1.   Run the stat -fc %T /sys/fs/cgroup/ command on the worker node:
o   For cgroup v2, the output is cgroup2fs.
o   For cgroup v1, the output is tmpfs.
2. Check if /sys/fs/cgroup/cgroup.controllers is present, then it is cgroup v2.

Identify the cgroup Version for Worker Pod

To check which cgroup version your worker pod uses:

1.   Login to the worker pod and check file /proc/$$/cgroup.
2. If the file has net_cls, then it's cgroup v1 otherwise it is cgroup v2.