sandboxpolicy: size the verdict ring buffers and report drops

Abierto
#1,107 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, kubernetes

Línea de trabajo

Start with enforce_file/program.bpf.c and its events ring buffer, then locate the privilege and network gadget buffers and the code that builds policy status and exports metrics. Measure event and drop rates under a file-heavy workload on AL2023 kernels 6.12 and 6.18, and record the buffer budget in the README. Done means drops appear in status and exported metrics, with a test that fills a buffer and verifies the report.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Follow-up from the review of #1075.

Problem

The file gadget sends its verdict events through one ring buffer of 256 KiB (events in enforce_file/program.bpf.c). Under a file-heavy workload the buffer can fill. A full buffer drops the event; the drop is counted (VERDICT_COUNT_DROPPED), but:

  • the size was not derived from a measured event rate;
  • a sustained drop rate is not visible in the policy status;
  • the same question applies to the privilege and network gadgets, which have their own buffers.

Enforcement itself is not affected: the hook decides before it reserves the event. What is lost is the verdict record (audit trail and export).

Proposal

  • Measure the event rate and the drop rate under a file-heavy workload on the fleet kernels (AL2023 6.12 and 6.18).
  • Size each section's buffer from that measurement, with a documented budget per node.
  • Report sustained drops in status (for example a Degraded notice with the drop count), and export the count.
  • Consider aggregating repeated identical allow verdicts in the kernel before they reach the buffer.

Done when

  • Buffer sizes are justified by a measurement recorded in the README.
  • A drop is visible in status and in the exported metrics.
  • A test fills the buffer and checks that the drop is reported.
Lenguaje dominante
Go
Estrellas
39
Forks
42
Merge medio
2 d 16 h
PR fusionados (30 d)
48

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de kubescape/node-agent

Todos los issues de kubescape/node-agent

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.