Falco eBPF Driver Config Schema¶
Note
This is auto-generated documentation from a JSON schema that is under construction, this will improve over time.
Return to the root config schema
https://raw.githubusercontent.com/elastisys/compliantkubernetes-apps/main/config/schemas/config.yaml#/properties/falco/properties/driver/else/properties/ebpf
Configuration for the Falco eBPF Driver.
| Abstract | Extensible | Status | Identifiable | Custom Properties | Additional Properties | Access Restrictions | Defined In |
|---|---|---|---|---|---|---|---|
| Can be instantiated | No | Unknown status | No | Forbidden | Forbidden | none | config/schemas/config.yaml* |
TYPE:
object (Falco eBPF Driver Config)
PROPERTIES:
| Property | Type | Required | Nullable | Defined by |
|---|---|---|---|---|
| hostNetwork | boolean |
Optional | cannot be null | Compliant Kubernetes Apps Config |
| path | string |
Optional | cannot be null | Compliant Kubernetes Apps Config |
hostNetwork¶
Needed to enable eBPF JIT at runtime for performance reasons. Can be skipped if eBPF JIT is enabled from outside the container
hostNetwork
-
is optional
-
Type:
boolean(Falco eBPF Host Network) -
cannot be null
-
defined in: Compliant Kubernetes Apps Config
TYPE:
boolean (Falco eBPF Host Network)
path¶
Path where the eBPF probe is located. It comes in handy when the probe have been installed in the nodes using tools other than the init container deployed with the chart.
path
-
is optional
-
Type:
string(Falco eBPF Path) -
cannot be null
-
defined in: Compliant Kubernetes Apps Config
TYPE:
string (Falco eBPF Path)
Return to the root config schema
Generated Sun Jun 23 03:48:25 UTC 2024 from elastisys/compliantkubernetes-apps@main