The Telco Partner CI team runs testing and certification for partners in the Telco industry.

As part of the CNF certification test suit, the OCP nodes are checked for kernel taints so the system won't pass the certification if they exist.

As we have observed, installing the Network Observability operator causes a warning kernel taint to appear and this will potentially impact our partners certification process.

Based on discussions in the #forum-ocp-network-observability and #proj-bpf-rhel channels the problem seems to be in the use of dynamically allocated maps.

4.12 - 4.16    

100%

    1. Deploy an OCP 4.14 cluster
    2. Open a debug console to one of the compute nodes.
    3. Check the kernel taint flag (file /proc/sys/kernel/tainted)
    4. Deploy the network observability operator (by the time of creating this issue, the latest netobserv-operator version was 1.4.2) and recheck the kernel taint flag.
    5. Reboot the node and recheck the kernel taint flag.
    6. Delete the netobserv-operator and recheck the kernel taint flag.
    

    3. flag is 0 (this decodes as "Kernel not Tainted").
    4. flag is 512 ("Kernel Issued Taint").
    5. flag is 512
    6. flag is 0

    3. flag is 0
    4. flag is 0
    5. flag is 0
    6. flag is 0