|
This is unreleased documentation for Network Enforcer 0.4-dev. |
Who is this project for? The personas.
This page lists the people who use Kubewarden Network Enforcer, and what each of them does with it. The use cases refer to these personas.
Kubewarden Network Enforcer personas
| Persona | Description |
|---|---|
Operator |
Installs Network Enforcer in a cluster and keeps it running. Selects the provider: Istio ambient, Calico, or Cilium. Connects the flow source and configures the telemetry collector. |
Platform engineer |
Owns the network posture of the cluster. Enables learning for the whole cluster. Decides when teams move their proposals to monitor mode and to protect mode. |
Namespace owner |
Owns one or more workloads. Reviews the proposal for a workload and approves it. Tunes the policy when a violation is expected traffic. Does not need cluster-wide permissions. |
Security engineer |
Reads the violations and the exported events. Looks for traffic that a workload did not produce before. Decides when a violation is a risk. |
Integrator |
Builds tools on top of Network Enforcer. Reads the custom resources and the OpenTelemetry events. Examples are a dashboard, a SIEM, or a GitOps pipeline. |
Developer |
Works on Network Enforcer itself. |